Automated New Relic Alert Coverage Audits
Every night, WebRun opens New Relic, lists the reporting entities and applications, checks each against your alert policies and conditions, opens a Trello card for every service with no coverage or no notification destination, and sends the blind spot list to WhatsApp.
How do I find services in New Relic with no alert coverage?
WebRun audits New Relic every night, listing your reporting entities and applications and matching each against your alert policies and conditions. It opens a Trello card for every service with no coverage or a dead notification route and messages the blind spot list to WhatsApp, so gaps close before a silent outage.
- Uncovered services are found before an outage finds them
- Dead notification routes are caught alongside missing conditions
- Every gap lands as one tracked Trello card, not a duplicate pile
Built for platform leads · SRE teams · DevOps engineers · engineering managers
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
one.newrelic.comin a real browser with your saved login - no setup, no API keys. -
1
New Relic - audit alert coverage
newrelic.com
WebRun opens New Relic to audit alert coverage. - Open New Relic and list the reporting entities and APM applications
- Open the alert policies and read the conditions attached to each
- Match every entity to the conditions covering it and mark the ones with none
- Check that each policy has a workflow and a live notification destination behind it
- Note anything covered by a condition whose notification route goes nowhere
Done when Every entity is marked as covered, uncovered, or covered with no notification route.
-
2
Trello - open a card per gap
trello.com
WebRun opens Trello to open a card per gap. - Open a card on the platform board for each service with no alert coverage
- Title it with the service name and whether the gap is a missing condition or a dead route
- Attach the entity type and the owning team so the card lands with someone
- Skip services that already have an open card so the board does not fill with duplicates
Done when Every coverage gap has one open Trello card.
-
3
WhatsApp - message the blind spots
whatsapp.com
WebRun opens WhatsApp to message the blind spots. - Send the platform lead a short list of tonight's uncovered services
- Lead with anything newly uncovered since last night
- Include the count of services still uncovered so the trend is obvious
Done when The platform lead has tonight's blind spot list on WhatsApp.
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 create or change alert conditions on its own?
No. WebRun only reads New Relic. It never creates a policy, edits a condition, or silences anything. The fix is proposed as an internal Trello card and a WhatsApp note, and a human makes the change.
How is this different from an incident digest?
An incident digest needs an alert to fire first. This audit looks for the services where no alert could fire at all, because no condition is attached or the notification route is dead.
Will it flood the board with duplicate cards?
No. It checks for an existing open card before creating one, so a long standing gap keeps a single card and only genuinely new gaps add to the board.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.