Alerts & routing
Sources
Section titled “Sources”| Source | Example |
|---|---|
| Threshold-overschrijding | CPU > 90% for 5 minutes |
| AI-anomalie | p99 latency 5× baseline |
| Heartbeat-stilte | No heartbeat in 90 seconds |
| Honeypot trip | Process reads /root/.aws/credentials-backup |
| CVE-match | New CVSS ≥ 7.0 on an installed package |
Routing
Section titled “Routing”Configured via Settings → Notifications. Per row: event type, channels, delay.
| Event | Channels | When |
|---|---|---|
| Critical incident | all channels | immediately |
| Honeypot trip | Slack #security + ntfy | immediately |
| Heartbeat silence | Slack + ntfy | ≥ 90 seconds |
| Warning incident | Slack + email | ≥ 5 minutes open |
| AI-anomalie (high conf.) | Slack #ai-insights | immediately |
Mute-windows
Section titled “Mute-windows”Snooze per alert (1 hour, 4 hours, 24 hours, end of incident) or per server. A muted incident does not escalate to PagerDuty.