Overview
Send Airbrake errors to Callgoose SQIBS. Airbrake posts to your SQIBS API endpoint every time a new error occurs, or a resolved error occurs again. SQIBS opens an incident titled with the error message.
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 AirBrake. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "error"."project"."id" |
(anything) | Opens an incident. |
| Title from | "error"."error_message" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
Airbrake does not send a message when you resolve an error, so close these incidents in SQIBS when the fix is out.
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 webhook in Airbrake
- In Airbrake, open the project and go to its Integrations tab. Under other integrations, choose Webhook.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=airbrake&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.
- Tick Enabled. To send production errors only, also tick the option that triggers only for environments matching
production. - Click Save.
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.
- Use the test option on the webhook integration, or raise an error in the project.
- In SQIBS, a new incident opens. Airbrake's payload looks like this (shortened):
{
"error": {
"id": 37463546,
"error_message": "RuntimeError: Payment service timed out",
"error_class": "RuntimeError",
"environment": "production",
"times_occurred": 1,
"project": {
"id": 1111,
"name": "shop-api"
}
},
"airbrake_error_url": "https://airbrake.io/projects/1111/groups/37463546"
}
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 Airbrake 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 Airbrake reports a timeout to a downstream service, SQIBS can run a workflow that checks the service and restarts it if it is not answering.
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.