Sign In

Monitor Automations

Create automations that respond to monitor status changes with actions like creating incidents, sending notifications, or updating status pages.

Prerequisites

1. Navigate to Automations

Go to Automations in the sidebar and click New Automation.

2. Select a Monitor Trigger

Choose a monitor status transition as the trigger:

Trigger When it fires
Success to Partial A monitor degrades from healthy to partially failing
Partial to Fail A partially failing monitor becomes completely down
Fail to Partial A down monitor begins recovering
Partial to Success A degraded monitor fully recovers
Success to Fail A monitor goes directly from healthy to down

3. Add Filters (Optional)

Narrow which monitors trigger this automation:

  • Monitor type - HTTP or Heartbeat
  • Monitor tags - Specific tag values
  • Linked catalog entities - Monitors associated with certain services

Filters help you create targeted automations for different service tiers or teams.

4. Configure Actions

Add actions to execute when the trigger fires:

Create Incident

Automatically create an incident with:

  • Pre-defined title and description
  • Severity level
  • Assigned responder or team

Send Notification

Alert team members via:

  • Slack channel or direct message
  • Email to specific addresses

Update Status Page

Reflect the status change on public status pages:

  • Set component status
  • Create a status update message

Add Delay

Wait before executing subsequent actions. Useful for:

  • Avoiding alerts for brief transient issues
  • Giving time for automatic recovery

5. Chain Multiple Actions

Actions execute in order. Common patterns:

Immediate alert with delayed escalation:

  1. Send Slack notification
  2. Add 5-minute delay
  3. Create incident (if still failing)

Full incident workflow:

  1. Create incident
  2. Send notification
  3. Update status page

6. Save and Enable

Click Save to activate the automation. It runs whenever a monitor matches the trigger and filter conditions.

Result

Your automation responds to monitor status changes automatically. Check Automations to view execution history and verify it’s working correctly.

Example Use Cases

Scenario Trigger Actions
Critical service down Success to Fail Create SEV-1 incident, notify on-call, update status page
Regional degradation Success to Partial Send Slack alert, wait 2 minutes
Recovery notification Fail to Success Add incident comment, send Slack notification
Customer-facing outage Partial to Fail Update status page, create incident