Automated Grafana Alert Coverage Checks
Every Monday, WebRun opens Grafana alerting, walks every folder of alert rules, traces each rule's labels through the notification policies to a contact point, lists the rules that would fire into nowhere, posts the coverage report to Telegram, and texts you when a silence has outlived its incident.
How do I check my Grafana alert rules actually notify someone?
WebRun checks your Grafana alerting setup every Monday. It walks every alert rule, traces its labels through the notification policies to a contact point, finds rules that would fire into nowhere, posts the coverage report to Telegram, and texts your on-call lead about silences left switched on.
- Rules that would fire into nowhere are named every Monday
- Silences left on past an incident get a same-week text
- Contact points nothing routes to stop cluttering the setup
Built for on-call leads · SRE teams · DevOps engineers · platform 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
grafana.comin a real browser with your saved login - no setup, no API keys. -
1
Grafana - trace every rule to a contact point
grafana.com
WebRun opens Grafana to trace every rule to a contact point. - Open Grafana alerting and list every alert rule by folder
- Read each rule's labels and trace them through the notification policy tree
- Note which contact point each rule would reach, and flag rules that match no policy
- Open the silences list and note any silence still active past its incident, with who created it
Done when Every alert rule has a named contact point or is flagged as routed nowhere.
-
2
Telegram - post the coverage report
telegram.org
WebRun opens Telegram to post the coverage report. - Post the coverage report to the on-call channel
- Lead with rules that reach no contact point at all
- List contact points that no rule routes to, so dead channels get cleaned up
- Link the folder for each flagged rule
Done when The on-call channel has this week's alert coverage report.
-
3
Twilio - text about stale silences
twilio.com
WebRun opens Twilio to text about stale silences. - Text the on-call lead when a silence has been active longer than your limit
- Name the silence, the rules it covers, and who created it
- Send nothing when every silence is inside its window
- Never delete a silence or edit a rule: WebRun reports, the on-call lead decides
Done when The on-call lead knows about every silence that outlived its incident.
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 my alert rules or delete silences?
No. WebRun reads the rules, policies, contact points and silences and reports what it finds. Editing a rule or lifting a silence stays with your on-call lead.
How does it know a rule reaches nobody?
It reads each rule's labels and follows them through the notification policy tree to a contact point. A rule whose labels match no policy route is reported as reaching nowhere.
How long before a silence counts as stale?
You set the limit, for example any silence active longer than seven days. Silences past that get a text with the rules they cover and who created them.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.