Automation Examples
Use these examples as starting points for your own automations.
Monitor Down - Create Incident
Automatically create an incident when a monitor goes down.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Monitor status changed |
| Condition | None (all monitors) |
| Action | Create incident |
Action details:
| Field | Value |
|---|---|
| Title | Monitor Down: {monitor.name} |
| Severity | P2 |
Variation - Production only:
Add a condition to limit to specific monitors:
| Component | Setting |
|---|---|
| Property | name |
| Operator | contains |
| Value | Production |
Heartbeat Failure - Create Incident
Create an incident when a scheduled job fails to check in.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Heartbeat status changed |
| Condition | None |
| Action | Create incident |
Action details:
| Field | Value |
|---|---|
| Title | Heartbeat Failed: {heartbeat.name} |
| Severity | P3 |
Incident Created - Notify Team
Send a notification when any incident is created.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Incident created or changed |
| Condition | None |
| Action | Send to recipient |
Action details:
| Field | Value |
|---|---|
| Recipient | On-call team |
| Message | New incident: {incident.title} |
Delayed Escalation
Wait before sending a follow-up notification.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Monitor status changed |
| Action 1 | Create incident |
| Action 2 | Set delay (5 minutes) |
| Action 3 | Send to recipient |
Action 1 details:
| Field | Value |
|---|---|
| Title | Monitor Down: {monitor.name} |
| Severity | P2 |
Action 2 details:
| Field | Value |
|---|---|
| Duration | 5 |
| Unit | Minutes |
Action 3 details:
| Field | Value |
|---|---|
| Recipient | Engineering Lead |
| Message | Escalation: {monitor.name} still down |
HTTP Monitors Only
Trigger only for HTTP type monitors.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Monitor status changed |
| Condition | monitorType == HTTP |
| Action | Create incident |
Multiple Conditions
Combine conditions for specific scenarios.
Configuration:
| Component | Setting |
|---|---|
| Trigger | Monitor status changed |
| Condition 1 | name contains “API” |
| Condition 2 | monitorType == HTTP |
| Conjunction | AND |
| Action | Create incident |
Customizing Examples
Replace Variables
Update placeholder values with your actual:
- Monitor names
- Team names
- Severity levels
- Notification recipients
Adjust Delays
Modify delay durations based on your response times and escalation policies.
Test First
Before publishing:
- Create the automation as a draft
- Verify the trigger and conditions
- Review the action configuration
- Publish when ready
Related
- Automations Overview - Understanding automations
- Triggers & Conditions - Configure triggers
- Actions & Delays - Configure actions
- Best Practices - Tips for effective automations