Overview
Send Observe monitor notifications to Callgoose SQIBS. A webhook notification action posts each new and ended notification to your SQIBS API endpoint. SQIBS opens an incident when a notification starts and resolves it when Observe reports it has ended.
How it works
isNew: true opens it, isEnded: true closes it.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 Observe. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "isNew" |
true |
Opens an incident. |
| Resolve | "isEnded" |
true |
Resolves the open incident. |
| Match | "Notification uuid" |
Ties the resolve message to the incident it opened. | |
| Title from | "Monitor" |
Becomes the incident title. | |
| Description from | "Description" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
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 a webhook action to a monitor
- In Observe, go to Monitors and create a monitor (for example a metric threshold) or edit one. Set its query and alert condition.
- Under the notification actions, click Add New Action and choose Webhook.
- Set the method to POST, add the header
Content-Type: application/json, and set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=observe&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.
- Edit the message body to this JSON (the list of variables is shown next to the editor):
{
"Notification": "{{notification.kind}}",
"Notification uuid": "{{notification.uuid}}",
"Monitor": "{{monitor.name}}",
"Importance": "{{monitor.notifyWhenDetails.importance}}",
"isNew": "{{notification.isNew}}",
"isEnded": "{{notification.isEnded}}",
"isReminder": "{{notification.isReminder}}",
"Description": "{{notification.description}}",
"URL": "{{{notification.url}}}"
}
- Save the action and the monitor. Make sure the monitor also notifies when a notification ends, so SQIBS can resolve it.
Step 3: 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.
- Set the monitor's threshold below the current value.
- In SQIBS, a new incident opens, titled with the monitor name. The payload looks like this:
{
"Notification": "Threshold monitor",
"Notification uuid": "4b1d2c9e-7a51-4f0e-9c8e-2d3f6a7b8c90",
"Monitor": "Container CPU",
"Importance": "Important",
"isNew": "true",
"isEnded": "false",
"isReminder": "false",
"Description": "container_cpu_usage_seconds_total is greater than 0.06 in the last 1m",
"URL": "https://123456789012.observeinc.com/workspace/41000000/monitor/42000000"
}
- When the condition clears, Observe sends
"isEnded": "true"with the same notification uuid, and SQIBS resolves the incident.
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 Observe webhook action.
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 Observe reports a container using too much CPU, SQIBS can run a workflow that restarts the container and records the before and after usage.
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.