Automated StackPath Bandwidth and WAF Report
Every Monday morning, WebRun opens the StackPath dashboard, reads the past week's bandwidth delivered, cache hit ratio, and requests blocked by the WAF for each site, logs the totals as a new row in Google Sheets, and posts a short written summary to a Notion page for the team.
How do I track my StackPath bandwidth and security activity every week?
Every Monday, WebRun reads the past week's bandwidth delivered, cache hit ratio, and WAF blocked requests for every StackPath site and logs the totals as a new row in Google Sheets. It also posts a short summary to a Notion page, flagging any site with a cache drop or a blocked request spike for the team to review.
- A full week of bandwidth and WAF data lands in one sheet automatically
- Cache hit ratio drops get flagged instead of discovered from a slow site
- The team gets a readable summary without opening the raw dashboard
Built for site reliability teams · security operations · web performance teams · StackPath customers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
stackpath.comin a real browser with your saved login - no setup, no API keys. -
1
StackPath - read bandwidth, cache, and WAF totals
stackpath.com
WebRun opens StackPath to read bandwidth, cache, and WAF totals. - Open the StackPath dashboard and go through each CDN and WAF enabled site
- Capture bandwidth delivered, cache hit ratio, and requests blocked by the WAF for the past 7 days
- Note any site with an unusually low cache hit ratio or a spike in blocked requests
Done when The past week's bandwidth, cache, and WAF figures are captured for every site.
-
2
Notion - log the week's totals to a sheet
notion.so
WebRun opens Notion to log the week's totals to a sheet. - Open the weekly tracking sheet in Google Sheets
- Add a new row per site with this week's bandwidth, cache hit ratio, and blocked request count
- Keep prior weeks in place so the trend stays visible
Done when This week's figures are logged as new rows alongside prior weeks.
-
3
Google Sheets - post the summary to Notion
google.com
WebRun opens Google Sheets to post the summary to Notion. - Post a short written summary to the team's StackPath page in Notion
- Call out any site with a cache hit ratio drop or a blocked request spike
- Link back to the full Google Sheets log for the detail
Done when The team's Notion page has this week's summary.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Does it change any CDN or WAF settings?
No. WebRun only reads bandwidth, cache, and WAF metrics and logs them. Changing a caching rule or a firewall setting always stays a step you take yourself.
What counts as an unusually low cache hit ratio?
You set the baseline for each site during setup, and WebRun flags anything that drops meaningfully below it in the weekly summary.
Can I track more than one site?
Yes. Every CDN and WAF enabled site on your StackPath account gets its own row each week, so the whole portfolio stays in one sheet.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.