alerts.routing.read. The source is taken to use the default policy; no incident opens and nothing is notified.
curl -X POST http://localhost:5080/api/v1/alerts/routing/test \
-H "authorization: Bearer $MS_TOKEN" \
-H "content-type: application/json" \
-d '{"labels": {"service.name": "checkout", "env": "prod"}, "severity": "critical"}'
{
"decision": {
"escalation_policy_id": "<policy-id>",
"team_id": "<team-id>",
"routing": { "reason": "rule", "rule_id": "<rule-id>", "rule_name": "Payments in production" }
},
"matched_rule_id": "<rule-id>",
"service": "default/checkout",
"service_team_id": "<team-id>",
"label_team_id": null
}
Alerting
Try routing
Work out which team and escalation policy an incident with a set of labels would get.
curl -X POST http://localhost:5080/api/v1/alerts/routing/test \
-H "authorization: Bearer $MS_TOKEN" \
-H "content-type: application/json" \
-d '{"labels": {"service.name": "checkout", "env": "prod"}, "severity": "critical"}'
{
"decision": {
"escalation_policy_id": "<policy-id>",
"team_id": "<team-id>",
"routing": { "reason": "rule", "rule_id": "<rule-id>", "rule_name": "Payments in production" }
},
"matched_rule_id": "<rule-id>",
"service": "default/checkout",
"service_team_id": "<team-id>",
"label_team_id": null
}
Last modified on October 31, 2026