Overview
Send Datadog monitor alerts to Callgoose SQIBS. You add SQIBS as a webhook in Datadog, then mention it in any monitor. When the monitor alerts, SQIBS opens an incident.
How it works
Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.
Step 1: Add the API filter in SQIBS
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Datadog. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "event_type" |
error |
Opens an incident. |
| Title from | "title" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template only opens incidents. To also resolve them automatically, add two fields to the Datadog payload in step 2 (alert_transition and alert_id), then add a Resolve filter: key "alert_transition" contains Recovered, and match on "alert_id".
The template is a starting point, not a lock-in: every value stays visible and you can change it.
In the API Integration window, click the round
{} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.Step 2: Add SQIBS as a webhook in Datadog
- In Datadog, open Integrations, find Webhooks and open its Configuration tab.
- Click New and set Name to
CallgooseSQIBS. - In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=datadog&token=<your-token>
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
- Keep the default Payload, or use this one, which adds what SQIBS needs to resolve incidents:
{
"body": "$EVENT_MSG",
"last_updated": "$LAST_UPDATED",
"event_type": "$EVENT_TYPE",
"title": "$EVENT_TITLE",
"date": "$DATE",
"org": {
"id": "$ORG_ID",
"name": "$ORG_NAME"
},
"id": "$ID",
"alert_id": "$ALERT_ID",
"alert_transition": "$ALERT_TRANSITION"
}
- Click Save.
Step 3: Send monitor alerts to SQIBS
In any monitor, add @webhook-CallgooseSQIBS to the notification message (Configure notifications & automations). Datadog then posts every alert of that monitor to SQIBS. Add it to as many monitors as you like.
Step 4: Test it
The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.
- Open a monitor that mentions
@webhook-CallgooseSQIBSand use Test Notifications, or let it alert. - In SQIBS, a new incident opens, titled from the Datadog event title.
- If you added the Resolve filter, the incident resolves when the monitor recovers.
No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the Datadog webhook.
Fix known issues automatically
Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a Datadog monitor reports a full disk, SQIBS can run a workflow that clears old logs and rechecks the space.
Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.
To set it up, in the same API filter:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.
Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.
Learn more:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.