Alert Configuration
Configure alerting channels, sensitivity, and escalation policies
Alert Channels
#
Connected
Slack
Post alerts to Slack channels with severity-based routing
PD
Connected
PagerDuty
Trigger PagerDuty incidents with auto-resolve on recovery
{}
Webhook
Send JSON payloads to any HTTP endpoint on anomaly detection
@
Connected
Email digests and critical alert notifications to your team
Detection Sensitivity
High
Fewer alerts, only major anomaliesCustom threshold configuration
Alert Rules
| Metric | Condition | Window | Severity | Status |
|---|---|---|---|---|
| cpu_usage | > 90% | 5min | critical | active |
| memory_usage | > 80% | 10min | warning | active |
| response_latency | > 500ms | 3min | critical | active |
| error_rate | > 5% | 5min | critical | active |
| disk_usage | > 85% | 15min | warning | paused |
| request_rate | anomaly_score > 0.8 | 5min | warning | active |
Escalation Policy
1
Notify on-call via Slack
2
Page via PagerDuty
3
Escalate to engineering lead
4
Notify VP Engineering