Weekly Better Stack reliability report for leadership
Every Monday morning, roll up last week's uptime, incidents, and worst outages into a leadership-ready summary in Slack and Notion.
Better Stack
Slack Bot
NotionEngineeringOperationsAI ReportsDaily DigestsEvery Monday at 9am, produce a weekly reliability report for leadership from Better Stack.
Start by using Better Stack's List Monitors to list every monitor. For each monitor that was not paused for the entire last seven days, pull its availability and SLA percentages for the last seven days using Get Monitor Availability with from/to set to the previous Monday through Sunday. Skip any monitor that was paused for the whole week so the report only reflects services that were actually being watched.
Then use Better Stack's List Incidents with a date range filter to pull every incident that was opened or resolved in the last seven days. For each incident capture its monitor, when it opened, when it resolved (if resolved), and its total duration. Rank the incidents by duration to find the worst outages, and for the top few pull their full timeline using List Incident Timeline so the write-up can describe what actually happened.
Write a stakeholder-friendly summary aimed at leadership, not engineers. It should include: a top-line uptime number for the week across all active monitors, the worst-performing services this week with their SLA and total downtime, what got better and what got worse versus last week, and notable incidents described in plain English (what broke, how long it lasted, how it resolved).
Then do two things with the summary. First, post a short executive recap to the Slack channel #reliability using Slack Bot Send a Message. Keep it tight: top-line uptime, worst services, a one-liner on each notable incident, and a link to the full Notion page. Second, create a new page in the 'Weekly reliability' Notion database using Notion Create a Page (parent = that database) so the archive is searchable. The page title should include the week ending date. Include the executive summary at the top followed by the full data: every monitor's availability and SLA for the week, every incident opened or resolved with its duration, and the timelines for the worst outages. Use Append Block Children if the full write-up needs to be added to the page after creation.
The Slack post is meant for scanning; the Notion page is the source of truth.
Additional information
What does this prompt do?
- Runs every Monday at 9am and reads uptime, SLA, and incident data for the last seven days from your Better Stack account
- Pulls incident timelines for the worst outages and writes a plain-English summary anyone on the leadership team can read
- Posts a short executive recap to a Slack channel and archives the full write-up as a searchable page in your Notion 'Weekly reliability' database
- Skips monitors that were paused all week so the report only reflects services you were actively watching
What do I need to use this?
- A Better Stack account with an Uptime API token
- A Slack workspace and a channel to post the executive summary in (for example #reliability)
- A Notion workspace with a 'Weekly reliability' database, shared with the connection
How can I customize it?
- Change the day or time the report runs
- Swap the Slack channel or broadcast to more than one channel
- Adjust what counts as a 'worst outage' (minimum duration, or how many incidents to feature in the summary)
Frequently asked questions
When does the report run?
What does the Slack summary include?
What ends up in Notion?
Does it include monitors that were paused all week?
Can non-engineers actually read the report?
Related templates
Every weekday at 8am, your billing team gets a Slack rundown of yesterday's failed Braintree charges, the revenue at risk, and who to chase first.
Every weekday morning, roll up your sprint's work items into a clear per-person standup summary and post it to your team's Slack channel before you meet.
Every three hours we scan Braintree for new disputes and chargebacks, open a tracked ticket with a tailored evidence checklist, and alert your team in Slack before the response deadline slips.
Every weekday morning we check your most important Databricks tables for freshness and data problems, and ping Slack only when something actually looks wrong.
Every Monday, automatically find which employee accounts on your company domain turned up in data breaches and get a plain-English briefing in Slack.
When a pipeline build fails, we post a tight Slack card naming who pushed, the likely cause, and a link to the build so on-call can triage in seconds.
Stop hand-writing your weekly reliability update.
Let Better Stack do the reporting and give your leadership team a summary they will actually read.