Overview

Send Backtrace crash and error alerts to Callgoose SQIBS. A webhook integration posts each alert to your SQIBS API endpoint, and SQIBS opens an incident for it.

You need
A Backtrace project with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Backtrace alerts open SQIBS incidents

How it works

Backtrace
Alert fires
An error threshold or issue-based alert fires.
Backtrace
Sends a webhook
Through a webhook integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the project.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose Backtrace. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "classifier".[0] alert Opens an incident.
Title from "project" Becomes the incident title.
Description from "text" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

Backtrace does not send a message when an alert clears, 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.

Find the right key with the JSON key creator
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 integration in Backtrace

  1. In Backtrace, open Project settings and go to Integrations under Workflow.
  2. Click + and choose Webhook. Give it a name, for example CallgooseSQIBS.
  3. In Server, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=backtrace&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.

  1. Click Next, choose the sections to include (for example Classifiers and Callstack), and click Submit.

Step 3: Create an alert that uses the webhook

  1. In Project settings, go to Alerts under Workflow and choose Error threshold alerts (or Issue-based alerts).
  2. Build the query in Explore, add an aggregation (for example on fingerprint), and export it as an Alert.
  3. Set the threshold and notification interval, choose the CallgooseSQIBS integration, 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.

  1. Send crashes until the threshold is reached, or lower the threshold for a test.
  2. In SQIBS, a new incident opens. Backtrace's payload looks like this (shortened):
{
  "classifier": [
    "alert"
  ],
  "project": "game-client",
  "universe": "example",
  "href": "https://example.sp.backtrace.io",
  "attributes": {
    "alertName": "Crash spike",
    "alertCriticalGroupCount": 1,
    "alertCriticalTriggerCount": 1
  }
}

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 Backtrace 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 Backtrace reports a crash spike after a release, SQIBS can run a workflow that rolls the service back to the previous version.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

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:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. 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: