Sign In

Monitor Automations

Trigger downstream actions based on monitor status transitions.

Upstat allows you to automate responses like incident creation, team notifications, or status page updates when a monitor’s status changes. Automations react to changes between Up, Partial, and Down states as determined by regional check results.

How Monitor Transitions Work

Monitor status in Upstat is calculated based on checks across all selected regions.

When a region reports a failure, a confirmation check is run after a short delay. If the region is still failing, the system evaluates the current results from all other regions:

  • If all regions are failing, the monitor transitions to Down
  • If some regions are failing but at least one is healthy, it is marked Partial
  • If all regions are reporting success, the monitor is considered Up

This model avoids false positives and reflects the real-world availability of your service more accurately.

Automation Triggers

Automations can respond to transitions between the three defined monitor states:

  • Up → Partial
  • Partial → Down
  • Down → Partial
  • Partial → Up
  • Up → Down

You can scope triggers further using filters like monitor type, tags, or linked catalog entities.

Example Use Cases

  • When a monitor goes Down, create a new incident and tag the associated service
  • If a monitor is Partial for more than a few minutes, notify the SRE team
  • Once a monitor returns to Up, add a comment to the related incident
  • For customer-facing services, create a status page update for any Down or Partial transition

Actions You Can Trigger

Each monitor automation can trigger one or more actions:

  • Create an Incident
  • Send a Notification (e.g. Slack, email)
  • Add Label to an existing incident
  • Add Comment to an incident
  • Create a Status Page Event
  • Add Delay before actions execute

Automations are flexible and allow chaining multiple actions.

Creating a Monitor Automation

  1. Go to the Automations section
  2. Click New Automation
  3. Select a monitor status transition (e.g. Up → Down) as the trigger
  4. Add optional filters:
    • Monitor tag
    • Monitor type
    • Linked catalog entity
  5. Add one or more actions
  6. Save and enable the automation

![Placeholder: Monitor Automation Setup Screenshot]

Best Practices

  • Use delays for Partial state transitions to reduce alert noise
  • Scope actions using tags and catalog entities to improve targeting
  • Combine with Incident Automations for follow-up handling
  • Regularly review automations for changes in infrastructure or team responsibilities

Summary

  • Automations respond to transitions between Up, Partial, and Down
  • Monitor state is determined by evaluating all assigned regions after confirmation
  • Trigger actions like incidents, notifications, or status updates
  • Reduce manual triage and respond consistently across teams

Learn more