All templates
For Site reliability engineers, DevOps teams & backend engineering teams

Catch a Loggly error rate spike as it happens

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.

  • 7-day free trial
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Checks every 5 minutes, day and night WebRun
1 Loggly check the error rate
2 Microsoft Teams post the spike alert
3 Trello create the investigation card
Run a sample
Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.loggly.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Loggly - check the error rate
    loggly.com
    WebRun in Loggly: check the error rate
    WebRun opens Loggly to 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.

  3. 2
    Microsoft Teams - post the spike alert
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: post the spike alert
    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.

  4. 3
    Trello - create the investigation card
    trello.com How to Automate Trello
    WebRun in Trello: create the investigation card
    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 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

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.loggly.com
ScheduleRuns automatically on this cadence
Checks every 5 minutes, day and night
DeliveryHow each run's result reaches you
Error spike alert · Microsoft Teams
OutputWhat each run produces - A Microsoft Teams alert the moment the error rate spikes, with a Trello card tracking the investigation.
Alert
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

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.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.