All templates
For DevOps teams, web performance teams & platform engineers

Get a daily digest of your Bunny.net CDN performance

Every morning, WebRun opens the Bunny.net panel, reads bandwidth used and cache hit ratio over the last 24 hours for every pull zone, logs the day's numbers on your infrastructure Calendar, and posts the same digest to Microsoft Teams.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:00 AM WebRun
1 Bunny.net check bandwidth and cache hit ratio
2 Google Calendar log the day's numbers
3 Microsoft Teams post the digest
Run a sample
In short

How do I track Bunny.net CDN bandwidth and cache performance daily?

WebRun checks every Bunny.net pull zone each morning, reading bandwidth used and cache hit ratio over the last 24 hours. It logs the day's numbers on your infrastructure Calendar and posts the same digest to Microsoft Teams, flagging the zone with the lowest hit ratio, so a caching problem gets noticed before your origin server absorbs the extra load.

  • Every pull zone gets a daily bandwidth and cache check
  • Low cache hit ratios get flagged before origin load spikes
  • A running performance history builds up on the Calendar

Built for DevOps teams · web performance teams · platform engineers · agencies managing CDN

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens panel.bunny.net in a real browser with your saved login - no setup, no API keys.

  2. 1
    Bunny.net - check bandwidth and cache hit ratio
    bunny.net
    WebRun in Bunny.net: check bandwidth and cache hit ratio
    WebRun opens Bunny.net to check bandwidth and cache hit ratio.
    • Open the Bunny.net panel and review every pull zone
    • Read bandwidth used and cache hit ratio for the last 24 hours
    • Note any zone with an unusually low hit ratio

    Done when Every pull zone has a current bandwidth and cache hit reading.

  3. 2
    Google Calendar - log the day's numbers
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: log the day's numbers
    WebRun opens Google Calendar to log the day's numbers.
    • Log the day's numbers as a note on your infrastructure calendar
    • Keep prior days' notes so trends over time are visible

    Done when Today's numbers are logged on the calendar.

  4. 3
    Microsoft Teams - post the digest
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: post the digest
    WebRun opens Microsoft Teams to post the digest.
    • Post the digest to your infrastructure channel
    • List every zone with its bandwidth and cache hit ratio
    • Flag the zone with the lowest hit ratio

    Done when The team has today's CDN digest in Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
panel.bunny.net
ScheduleRuns automatically on this cadence
Every day at 7:00 AM
DeliveryHow each run's result reaches you
CDN digest · Microsoft Teams
OutputWhat each run produces - A daily digest of bandwidth and cache hit ratio per pull zone.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it purge a cache or change a pull zone setting on its own?

No. WebRun only reads bandwidth and cache data and reports it. Purging a cache or changing a pull zone setting always stays a manual step in Bunny.net.

What counts as an unusually low cache hit ratio?

A clear drop from that zone's normal pattern, which usually means more requests are reaching your origin server than they should.

Does it cover every pull zone on the account?

Yes. It reviews every pull zone under the account each morning, not just your busiest one.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.