Automated Honeycomb SLO Burn Rate Scorecard
Every Friday, WebRun opens Honeycomb, compiles the week's burn rate against every defined SLO, books a recurring SLO review slot on the calendar with this week's numbers attached, and posts the scorecard to Microsoft Teams so the team sees which services are eating into their error budget before it becomes a real problem.
How do I track weekly SLO burn rate across my Honeycomb services?
WebRun compiles your week's Honeycomb SLO burn rate every Friday, service by service. It keeps a recurring SLO review slot booked on the calendar with the scorecard attached, and posts the full breakdown to Microsoft Teams, so the team sees which services are eating into their error budget before it becomes a real problem.
- SLOs trending toward exhaustion get flagged before the budget runs out
- The review meeting always has this week's burn rate ready
- Error budget health is visible without querying Honeycomb directly
Built for SRE teams · platform teams · engineering managers · observability teams
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
ui.honeycomb.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Honeycomb - compile the week's SLO burn rate
- Open Honeycomb and check the current burn rate for every defined SLO
- Record the remaining error budget for each
- Flag any SLO whose burn rate is trending toward exhausting its budget
Done when Every defined SLO has this week's burn rate and remaining budget.
-
2
Google Calendar - book the SLO review
calendar.google.com
WebRun opens Google Calendar to book the SLO review. - Confirm the recurring SLO review slot is still on the calendar
- Attach this week's burn rate scorecard to the event description
- Reschedule only if the slot was removed
Done when The SLO review event exists with this week's scorecard attached.
-
3
Microsoft Teams - post the scorecard to the team
microsoft.com
WebRun opens Microsoft Teams to post the scorecard to the team. - Post the burn rate scorecard for every SLO to the engineering channel
- Show which SLOs are trending toward exhausting their budget
- Note the week over week change for each
Done when The engineering channel has this week's full SLO scorecard.
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
Will it change any SLO definitions or thresholds?
No. WebRun only reports the burn rate against SLOs your team already defined. Changing a definition is always your team's call.
What happens if an SLO is close to exhausting its budget?
It gets flagged clearly in both the Teams post and the calendar event, so it doesn't get missed at the review.
Does this replace real time SLO alerting?
No. This is a weekly summary for the review meeting. Honeycomb's own real time alerts still handle immediate burn rate spikes.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.