Overview

Send Sentry issue alerts to Callgoose SQIBS. A Sentry internal integration with a webhook URL becomes an action you can add to any alert rule. When the rule fires, SQIBS opens an incident.

You need
A Sentry organization where you can create integrations (Manager or Owner), and a SQIBS API token
Setup time
About 10 minutes
Result
Sentry alerts open SQIBS incidents

How it works

Sentry
Alert fires
An issue alert rule fires, for example on a new issue.
Sentry
Sends a webhook
The internal integration posts it as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
triggered opens it.

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 Sentry. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "action" triggered Opens an incident.
  1. Choose the Priority for these incidents and click Save.

To give the incident a useful title, set Incident title from to "data"."event"."title". Sentry alerts only fire; resolve the incident in SQIBS when the issue is fixed, or let an automation workflow do it.

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: Create an internal integration in Sentry

  1. In Sentry, go to Settings > Developer Settings > Custom Integrations and click Create New Integration, then choose Internal Integration.
  2. Name it Callgoose SQIBS.
  3. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=sentry&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. Turn on Alert Rule Action, so the integration can be chosen in alert rules.
  2. Save the integration.

Step 3: Add SQIBS to an alert rule

  1. Go to Alerts > Create Alert and choose an issue alert, for example Issues.
  2. Set the conditions, for example WHEN a new issue is created.
  3. In THEN, add the action Send a notification via Callgoose SQIBS.
  4. Name the rule and click Save Rule.

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. Use Send Test Notification on the alert rule, or trigger an error in a test project.
  2. In SQIBS, a new incident opens. Sentry's issue alert payload looks like this (shortened):
{
  "action": "triggered",
  "data": {
    "event": {
      "title": "TypeError: Cannot read properties of undefined",
      "issue_id": "1170820242",
      "web_url": "https://sentry.io/organizations/<org>/issues/1170820242/events/<event>/",
      "level": "error"
    },
    "triggered_rule": "New issue in checkout"
  }
}

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 Sentry 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 Sentry reports a crash loop in a worker, SQIBS can run a workflow that restarts the worker and attaches its recent logs.

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: