Overview
Send ObservePoint run notifications to Callgoose SQIBS. ObservePoint calls a webhook when an audit or journey run completes. SQIBS opens an incident for it, so the run's results reach the on-call or analytics team without anyone watching the dashboard.
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.
- Add a filter with these values (there is no built-in ObservePoint template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "itemType" |
Opens an incident for each completed run. | |
| Match | "runId" |
One incident per run. | |
| Title from | "itemType" |
Becomes the incident title (audit or journey). |
- Choose the Priority for these incidents and click Save.
ObservePoint's webhook carries only the run and item IDs, not the results. Use a low priority, and open the run in ObservePoint from the IDs. Send only the audits whose results need a person.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 the webhook to an audit or journey
- In ObservePoint, open the audit (or journey) and its settings.
- In Complete Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=observepoint&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.
- Click Save Audit, or Save Audit and Run Now to test straight away.
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.
- Run the audit.
- When it completes, a new incident opens in SQIBS. The payload looks like this:
{
"runId": 4912238,
"itemType": "audit",
"itemId": 1381612
}
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 audit's webhook URL.
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 an audit run completes, SQIBS can run a workflow that fetches the run summary from the ObservePoint API and adds it to the incident.
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.