Routing Grafana alerts into MonoDuty

Yes, and that is the cleanest path. Grafana lets you customise the body a webhook contact point sends, so you can emit our shape directly: 1. In Grafana, edit your contact point and switch it to send a custom payload. 2. Emit a JSON object with exactly title, severity and description. Populate title from your alert name and instance labels, description from the annotations, and set severity to one of CRITICAL, HIGH, MEDIUM or LOW. Uppercase matters, anything else is discarded. 3. Keep the alert trigger's predefined values sensible anyway, since they are what you get if a field is missing. 4. Consider creating one alert trigger per service rather than one for everything. That way the incident source tells you which system fired even before you read the title, and you can subscribe different notification channels per service. If customising the payload in Grafana is awkward in your setup, the alternative is a small relay endpoint of your own that receives Grafana's body and posts ours. Same idea, just moved one hop. One behaviour to design around: each fire creates a new incident, there is no grouping by alert name. If a Grafana alert re-fires on every evaluation interval you will get one incident per evaluation, so set your Grafana repeat interval accordingly.