Use case: monitoring stack

Phone Calls for Prometheus and Grafana Alerts

Edesy OnCall gives you a webhook URL for Prometheus Alertmanager or Grafana alerting. Route your critical alerts to it and each firing alert opens an incident that phones your on-duty engineer in English or Hindi, escalating until someone presses 1. A resolved alert closes the incident. Keep chat and email for everything else.

1 URL

Per alert webhook monitor

Auto

Format detection

Resolved

Closes the incident

Free

For 3 monitors

Alertmanager and Grafana detected automatically

Grouped by fingerprint

Escalates until someone presses 1

Alert webhooks at a glance

What happens to an alert your stack sends

ItemEdesy OnCall
EndpointPOST https://oncall.edesy.in/ingest/<token>, one URL per alert webhook monitor
FormatsPrometheus Alertmanager webhook, Grafana alerting webhook, Uptime Kuma, or generic JSON; detected automatically
Firing alertOpens an incident (or updates the open one with the same key) and starts the monitor's escalation policy
Resolved alertCloses the matching incident; paged contacts get a back-up email
GroupingBy Alertmanager fingerprint, or alertname + instance + job when there is no fingerprint
What the call saysThe alert's summary annotation, or its alertname, plus your organisation name
Limits120 requests a minute per IP, 1 MB body

Route critical alerts to a phone call

Your stack keeps doing the detection

  1. Step 1 of 5: Create an alert webhook monitor

    In OnCall, add an Alert webhook monitor, attach an escalation policy and copy its URL.

  2. Step 2 of 5: Add it as a receiver

    In Alertmanager, add a webhook_configs receiver with send_resolved: true. In Grafana, add a Webhook contact point.

  3. Step 3 of 5: Route only what deserves a call

    Send severity=critical (or your equivalent) to the OnCall receiver, and keep warnings in chat or email.

  4. Step 4 of 5: Write a speakable summary

    Set a short summary annotation such as "Checkout API error rate above 5%". It is what the on-call engineer hears.

  5. Step 5 of 5: Test it

    Fire a test alert from Grafana or amtool and check the incident timeline in OnCall.

Why add a phone call to your stack

  • Chat channels get muted, and email is read in the morning

  • Press 1 tells the team someone owns the incident

  • A second step calls the next engineer if the first is asleep

  • Hindi alerts for teams who prefer them

What stays in your stack

  • Detection, thresholds and alert rules stay in Prometheus or Grafana

  • Chat notifications stay in your existing contact points

  • OnCall has no schedules or rotations: edit the policy when duty changes

  • No SMS, Slack or Teams from OnCall: calls and email only

Setup guides

Step by step for each tool

Prometheus and Grafana phone call alerts: FAQ

Wiring OnCall into a larger stack?

Tell us what you run and how alerts are routed today. We reply within one working day.

Make critical alerts ring a phone

Create an alert webhook monitor on the Free plan and route one critical alert to it. Prices exclude 18% GST.