Automated Loggly Error Rate Spike Alerts
Every few minutes, WebRun checks Loggly for a jump in error-level log entries across your applications, posts a Microsoft Teams alert naming the affected application and the spike size, and creates a Trello card so the investigation is tracked from the first alert until it is resolved.
How do I get alerted immediately to a Loggly error rate spike?
WebRun checks Loggly every few minutes for a jump in error-level log entries, posting a Microsoft Teams alert naming the application and spike size the moment it happens. It also creates a Trello card to track the investigation from the first alert through to resolution, so a real error spike gets both immediate visibility and a paper trail.
- An error spike gets a Teams alert within minutes of starting
- Every spike has a tracked Trello card from alert to resolution
- Normal log noise does not trigger unnecessary alerts
Built for Site reliability engineers · DevOps teams · backend engineering teams · platform 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
www.loggly.comin a real browser with your saved login - no setup, no API keys. -
1
Loggly - check the error rate
- Open Loggly and review the rate of error-level log entries across applications for the last 15 minutes
- Compare it against the normal baseline for that application
- Flag any application spiking well above baseline
Done when Every application with an error rate spike is identified with its current and baseline rate.
-
2
Microsoft Teams - post the spike alert
microsoft.com
WebRun opens Microsoft Teams to post the spike alert. - Post an alert to the monitoring channel in Microsoft Teams
- Include the application name, the current error rate, and how far above baseline it is
- Link to the relevant Loggly search
Done when The team has a Teams alert for the current error rate spike.
-
3
Trello - create the investigation card
trello.com
WebRun opens Trello to create the investigation card. - Open the Log Investigations Trello board
- Create a card for the spike with the application and a link to Loggly
- Place it in the To Investigate column
Done when A Trello card exists for every current error rate spike.
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 WebRun deploy a fix or roll back a release?
No. It only detects the spike, alerts the team, and tracks the investigation. Any fix or rollback is a decision made by your engineering team.
What counts as a spike?
An error rate for an application that jumps well above its own recent baseline, so normal daily variation does not trigger a false alarm.
Does it create a new card for an ongoing spike?
No. If a card is already open for that spike, WebRun will not create a duplicate until it clears and a new spike happens.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.