Automated New Relic Incident Digest
Every morning, WebRun opens New Relic, checks alerts opened in the last 24 hours and compares key service error rates and response times to baseline, exports the incident report to Drive, and posts a summary to Slack.
How do I get a daily digest of open New Relic alerts?
WebRun checks New Relic every morning for alerts opened in the last 24 hours and compares key service error rates and response times to baseline. It exports the full incident report to Google Drive and posts a Slack summary naming the worst-performing service, so engineering starts the day knowing exactly what needs attention.
- Engineering starts the day with a clear incident summary, not raw alerts
- The worst-performing service is called out automatically each morning
- A full report is saved to Drive for anyone who needs the detail
Built for site reliability engineers · DevOps teams · engineering managers · on-call engineers
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 - check open alerts and error rates
newrelic.com
WebRun opens New Relic to check open alerts and error rates. - Open New Relic and list alerts opened in the last 24 hours
- Check current error rate and response time against baseline for key services
- Note which service is furthest from its usual baseline
Done when Every open alert and key service has been checked.
-
2
Google Drive - export the incident report
drive.google.com
WebRun opens Google Drive to export the incident report. - Export the incident list with alert details to the shared Drive folder
- Name the file with the date so history stays searchable
Done when This morning's incident report is saved to Drive.
-
3
Slack - post the summary
slack.com
WebRun posts to Slack to share the summary. - Post a summary of open alerts and the worst-performing service to the engineering channel
- Link to the saved report in Drive
Done when The team has this morning's incident digest in Slack.
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 resolve or acknowledge alerts on its own?
No. WebRun only reports what's open. Acknowledging, resolving, or paging further escalation is left to your on-call process.
How does it pick the worst-performing service?
It compares each key service's current error rate and response time to its own baseline, so the digest highlights the service furthest from normal, not just the loudest alert.
What if there are no open alerts?
The digest still posts, noting all services are within baseline, so a quiet morning is confirmed rather than assumed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.