Overview
Send StatusCake test alerts to Callgoose SQIBS. StatusCake's own webhook posts form data, not JSON, so SQIBS uses StatusCake's Microsoft Teams integration instead: it posts a JSON card to any URL you give it. SQIBS opens an incident when a test goes down and resolves it when it is up again.
How it works
attention opens it, good 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 Statuscake. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "attachments".[0]."content"."body".[0]."style" |
attention |
Opens an incident. |
| Resolve | "attachments".[0]."content"."body".[0]."style" |
good |
Resolves the open incident. |
| Match | "type" |
Ties the resolve message to the incident it opened. | |
| Title from | "attachments".[0]."content"."body".[0]."items".[0]."text" |
Becomes the incident title. | |
| Description from | "attachments".[0]."content"."body".[2]."facts".[1]."value" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template matches the resolve message on "type", which is always message, so every test shares one incident and any recovery resolves it. Change Map incident with (trigger and resolve) to the test name, "attachments".[0]."content"."body".[0]."items".[0]."text", so each test has its own incident.
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 the integration in StatusCake
- In StatusCake, go to Alerting > Integrations and click New Integration.
- Set Integration Type to Microsoft Teams and give it a name, for example
CallgooseSQIBS. - In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=statuscake&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 Integration.
Step 3: Use it in a contact group
- Go to Alerting > Contact Groups, and create a group or edit one (for example Default Contact Group).
- In Integrations, select
CallgooseSQIBSand save the group. - In each test (Uptime > New Uptime Test, or an existing test), choose this contact group under Alert Settings, and save.
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.
- Point a test at an address that does not answer, or pause the site behind it.
- In SQIBS, a new incident opens, titled with the test name. The card looks like this (shortened):
{
"type": "message",
"attachments": [
{
"contentType": "application/vnd.microsoft.card.adaptive",
"content": {
"type": "AdaptiveCard",
"body": [
{
"type": "Container",
"style": "attention",
"items": [
{
"type": "TextBlock",
"text": "Shop - shop.example.com"
}
]
},
{
"type": "TextBlock",
"text": "Your website **Shop** went down!"
},
{
"type": "FactSet",
"facts": [
{
"title": "HTTP Code:",
"value": "503"
},
{
"title": "Reason:",
"value": "Service Unavailable"
}
]
}
]
}
}
]
}
- When the test is up again, the card style is
goodand 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 StatusCake integration.
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 StatusCake reports the site down, SQIBS can run a workflow that restarts the web server and rechecks the page.
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.