Core Concepts
Alert Configurations
Create alert rules with thresholds, severity, and trigger routing
Alert configurations define when notifications should be sent for a monitor.
Required settings
Each configuration needs:
- monitor
- alert type (
STATUS,LATENCY, orUPTIME) - alert value
- failure threshold
- success threshold
- at least one trigger
Alert value by type
| Alert type | Value format |
|---|---|
STATUS |
DOWN or DEGRADED |
LATENCY |
latency threshold in milliseconds |
UPTIME |
minimum uptime percentage |
Threshold behavior
- Failure threshold: consecutive failing evaluations before
TRIGGERED - Success threshold: consecutive passing evaluations before
RESOLVED
Higher thresholds reduce noise; lower thresholds detect faster.
Severity and incidents
- Severity is
CRITICALorWARNING. - Optional incident creation links alert events to incidents.
Common patterns
Critical outage alert
- Type:
STATUS - Value:
DOWN - Failure threshold:
1 - Success threshold:
2 - Severity:
CRITICAL
Performance alert
- Type:
LATENCY - Value:
1000 - Failure threshold:
3 - Success threshold:
5 - Severity:
WARNING
Troubleshooting
- Not triggering: verify configuration is active and conditions actually fail consecutively
- Not resolving: verify success threshold and check for intermittent failures
- No notifications: verify attached trigger is active and correctly configured