Webhooks: a JSON alert to your endpoint when a synthetic monitor fires
A generic alert sink posts each synthetic-monitor alert at or above your minimum severity as a JSON body to the URL you set. There is no HMAC signature, no custom header, no event choice and no run-completion event yet.
Which way the data flows
Dokimore to your endpoint; nothing is fetched from it.
Set it up
- Prepare an HTTPS endpoint that accepts a JSON POST, and treat its URL as a secret.
- In Developer Experience, open Monitoring, then Alert Sinks, and add a generic webhook sink with the URL and a minimum severity.
- Let a monitor raise an alert and read the body your endpoint receives before you build on its fields.
Where it stops
Stated plainly
- The request is not signed, so the URL itself is the only secret.
- Delivery leaves from the platform’s servers in India; an endpoint on a private network needs a reachable relay.
Questions buyers ask
Are run completions or failures sent?
No. Only synthetic-monitor alerts are sent to a sink today.
Can a mailbox receive the alerts?
Not from an alert sink. Use a webhook-to-email relay on your side if a mailbox must receive them.
Where it is implemented
The files in our code that carry this integration. A catalogue test checks that each still exists, so this page cannot outlive the feature.
backend/src/modules/developer-experience/services/alert-sink-dispatcher.tsbackend/src/modules/developer-experience/routes/alert-sinks.tsbackend/src/modules/developer-experience/services/synthetic-monitoring.ts
Related pages
Also under Alerting and chat: Slack · Microsoft Teams · PagerDuty · Opsgenie
Try it against your own pipeline
Free plan, no card; the integrations on this page are on every plan.