Route Matcher nach Labels
{
"labels": {
"team": "platform",
"env": "prod",
"severity": "critical"
}
}
Generische Webhook-Nutzlast
{
"external_id": "deploy-check-42",
"title": "Billing API error rate is high",
"message": "Error rate exceeded the production threshold for 10 minutes.",
"status": "firing",
"severity": "critical",
"labels": {
"team": "payments",
"service": "billing-api",
"env": "prod",
"alertname": "HighErrorRate"
},
"event_link": "https://monitoring.example.com/alerts/deploy-check-42"
}
Gruppieren Sie nach stabilen Feldern
["alertname", "service", "env"]
Schweigen durch Etiketten
{
"labels": {
"service": "billing-api",
"env": "staging"
}
}
Filter für den Schweregrad des Kanals
{
"notify_on_severities": ["critical", "high"]
}
Alertmanager Empfänger Idee
Erstellen Sie separate Alertmanager-Empfänger für verschiedene IncidentRelay-Route-Token, wenn Alarmklassen zu verschiedenen Routen oder Kanälen gehen sollen.