Overview
Send DebugBear results to Callgoose SQIBS. A project webhook posts each completed test to your SQIBS API endpoint. SQIBS opens an incident when a page test fails (for example a broken page or a missed performance budget) and resolves it when the page is back to normal.
How it works
failure opens it, neutral 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 DebugBear. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "result"."status" |
failure |
Opens an incident. |
| Resolve | "result"."status" |
neutral |
Resolves the open incident. |
| Match | "page"."id" |
Ties the resolve message to the incident it opened. | |
| Title from | "page" |
Becomes the incident title. | |
| Description from | "result"."oneLineSummary" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template titles the incident with the whole "page" object. Change Incident title from to "page"."name" for a short title.
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 in DebugBear
- In DebugBear, open Project settings > Integrations and click Create webhook.
- Give it a name and enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=debugbear&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.
- Set the status filter so both failures and recoveries are sent, choose the test types, and click Save.
Step 3: Monitor a page
If you do not have one yet, click Add page, enter the URL, the device and the test schedule, and save. Results now go to SQIBS.
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.
- Run a test on a page that breaks a budget, or wait for the next scheduled test.
- In SQIBS, a new incident opens. DebugBear's payload looks like this (shortened):
{
"event": "testComplete",
"page": {
"id": "381109",
"name": "Shop home",
"url": "https://shop.example.com",
"region": "us-east"
},
"result": {
"status": "failure",
"oneLineSummary": "Largest Contentful Paint 6.1 s, over the 4 s budget",
"url": "https://www.debugbear.com/viewResult/abc/overview"
}
}
- When the next test is back to normal, DebugBear sends
"status": "neutral"for the same page, 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 DebugBear 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 DebugBear reports the home page has become slow, SQIBS can run a workflow that purges the CDN cache and warms the page again.
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.