Webhooks#
Webhooks send Reply CMP notifications to Microsoft Teams, PagerDuty or any HTTPS endpoint. Open Tenant → Webhooks.
They are used by alert rules, budgets, cost spike alerts and reports. Events include Alert Fired / Resolved, Budget Threshold Reached, Budget Forecast Exceeded, Anomaly Detected, Report Ready and Report Generation Failed.
Channel types#
Type |
Delivery |
Use for |
|---|---|---|
Webhook |
HTTPS POST with a JSON payload, optionally signed |
Custom receivers, Slack, Opsgenie… |
Microsoft Teams |
HTTPS POST with a message card |
Teams channels |
PagerDuty |
Events API v2 |
Opening and auto-resolving incidents |
Add an integration#
Click Add integration.
Fill in:
Field
Description
Name
Up to 64 characters
Type
Webhook, Microsoft Teams or PagerDuty
Endpoint URL
HTTPS URL (not for PagerDuty)
Signing secret
Optional (Webhook, Teams): adds an
X-Reply-CMP-SignatureHMAC-SHA256 headerRouting Key
PagerDuty only: the 32-character integration key
Send a test delivery, then save.
Then select the webhook in the notification settings of an alert rule, budget or spike alert. One webhook can serve many rules, and one rule can use many webhooks.
Manage#
Send test delivery — check connectivity; the result shows the HTTP status or error.
Delivery history — the last 200 attempts, with event, status, HTTP code and error.
Enabled switch — pause deliveries without detaching the webhook.
Delete — removes it from every rule, with its history. This cannot be undone.
Each tenant can have up to 20 webhooks.
PagerDuty#
In PagerDuty, open Services → Service Directory → your service → Integrations → Add integration → Events API v2.
Copy the Integration Key.
In Reply CMP, add a PagerDuty integration with that key as Routing Key and send a test.
A firing alert opens an incident; resolving the alert closes it. Each rule has at most one open incident, and the rule’s notification cooldown applies.
Security#
Only
https://URLs are accepted.URLs resolving to private, loopback or link-local addresses are rejected.
With a signing secret, verify
X-Reply-CMP-Signature(HMAC-SHA256 of the raw body) on your receiver.
Having trouble? See Troubleshooting → Webhooks.