Alerting — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— Alerting & On-Call
📋Route
⚙️Group
🔄Severity
✅Receivers
🎯 Next: Test →
Step 1 / 4
Speed
Route Configuration
RouteTree routes alerts to different receivers based on labels💡 Analogy
Like an emergency call center routing system — fire calls go to fire dept, minor incidents to non-emergency line.
AlertManager routes alerts based on label matching. Critical → PagerDuty (page on-call). Warning → Slack (no wake-up). Default → monitoring channel.
Console Output
> Alert: HighErrorRate (severity=critical)
> Route match: severity=critical → pagerduty
> Alert: SlowResponses (severity=warning)
> Route match: severity=warning → slack-alerts
●alertmanager.yml
Route ConfigurationL4–12
1# AlertManager routing configuration
2global:
3  resolve_timeout: 5m
4 
5route:
6  group_by: ['alertname', 'cluster', 'service']
7  group_wait: 30s      # wait before sending first notification
8  group_interval: 5m   # time between grouped notifications
9  repeat_interval: 4h  # re-notify if still firing after 4h
10  receiver: default
11  routes:
12    # Critical alerts → PagerDuty immediately
13    - match:
14        severity: critical
15      receiver: pagerduty
16      group_wait: 10s   # faster for critical
17 
18    # Warning alerts → Slack only (no on-call wake-up)
19    - match:
20        severity: warning
21      receiver: slack-alerts
22 
23receivers:
24  - name: pagerduty
25    pagerduty_configs:
26      - service_key: $PAGERDUTY_KEY
27        send_resolved: true     # also notify when alert resolves
28        description: "{{ .CommonAnnotations.summary }}"
29 
30  - name: slack-alerts
31    slack_configs:
32      - channel: '#alerts'
33        api_url: $SLACK_WEBHOOK
34        text: "{{ range .Alerts }}{{ .Annotations.summary }}{{ end }}"
35        send_resolved: true
36 
37  - name: default
38    slack_configs:
39      - channel: '#monitoring'
39 lines
Timeline — 4 Steps
Route Configuration
RouteTree routes alerts to different receivers based on labels💡 Analogy
Like an emergency call center routing system — fire calls go to fire dept, minor incidents to non-emergency line.
AlertManager routes alerts based on label matching. Critical → PagerDuty (page on-call). Warning → Slack (no wake-up). Default → monitoring channel.
Console Output
> Alert: HighErrorRate (severity=critical)
> Route match: severity=critical → pagerduty
> Alert: SlowResponses (severity=warning)
> Route match: severity=warning → slack-alerts

Was this page helpful?

Discussion

RouteTree routes alerts to different receivers based on labels

💡 Analogy

Like an emergency call center routing system — fire calls go to fire dept, minor incidents to non-emergency line.

AlertManager routes alerts based on label matching. Critical → PagerDuty (page on-call). Warning → Slack (no wake-up). Default → monitoring channel.

Console Output

> Alert: HighErrorRate (severity=critical)
> Route match: severity=critical → pagerduty
> Alert: SlowResponses (severity=warning)
> Route match: severity=warning → slack-alerts

RouteTree routes alerts to different receivers based on labels

💡 Analogy

Like an emergency call center routing system — fire calls go to fire dept, minor incidents to non-emergency line.

AlertManager routes alerts based on label matching. Critical → PagerDuty (page on-call). Warning → Slack (no wake-up). Default → monitoring channel.

Console Output

> Alert: HighErrorRate (severity=critical)
> Route match: severity=critical → pagerduty
> Alert: SlowResponses (severity=warning)
> Route match: severity=warning → slack-alerts