Overview

Send Uptrace alerts to Callgoose SQIBS. A webhook notification channel posts every alert state change to your SQIBS API endpoint. SQIBS opens an incident when an alert opens and resolves it when Uptrace closes it.

You need
An Uptrace project (cloud or self-hosted), and a SQIBS API token
Setup time
About 10 minutes
Result
Uptrace alerts open and resolve SQIBS incidents

How it works

Uptrace
Alert fires
A metric or error monitor fires.
Uptrace
Sends a webhook
Through a webhook channel, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
State open opens it, closed 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

  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 Uptrace. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "alert"."state" open Opens an incident.
Resolve "alert"."state" closed Resolves the open incident.
Match "alert"."id" Ties the resolve message to the incident it opened.
Title from "alert"."type" Becomes the incident title.
Description from "alert"."name" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The template titles the incident with the alert type (for example error). Set Incident title from to "alert"."name" and Incident description from to "alert"."url" so the incident says what fired and links to 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: Add a webhook channel in Uptrace

  1. In Uptrace, go to Alerting > Notification Channels and click New Channel. Choose Webhook.
  2. Give it a name, and in Webhook URL enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=uptrace&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. Optional: add your own key-value pairs to the JSON payload, for example "service": "checkout".
  2. Choose the monitors that use this channel (create monitors under Alerting > Monitors) and click Create.

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.

  1. Let a monitor fire, or lower its threshold for a test.
  2. In SQIBS, a new incident opens. Uptrace's payload looks like this:
{
  "id": "8ac2",
  "eventName": "created",
  "payload": null,
  "createdAt": "2026-11-22T10:20:00Z",
  "alert": {
    "id": "181374",
    "url": "https://app.uptrace.dev/alerting/1/alerts/181374",
    "name": "ERROR connection refused to payments-db",
    "type": "error",
    "state": "open",
    "createdAt": "2026-11-22T10:22:20Z"
  }
}
  1. When the alert closes, Uptrace sends "state": "closed" with the same alert id, 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 Uptrace channel.

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 Uptrace reports connection errors to a database, SQIBS can run a workflow that checks the database and restarts the connection pooler.

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: