Overview

Send InfluxDB alerts to Callgoose SQIBS. An HTTP notification endpoint and a notification rule post each check status change to your SQIBS API endpoint. SQIBS opens an incident when a check goes to CRIT and resolves it when the check is OK again.

You need
InfluxDB 2.x (OSS or Cloud) with checks, and a SQIBS API token
Setup time
About 15 minutes
Result
InfluxDB checks open and resolve SQIBS incidents

How it works

InfluxDB
Alert fires
A check's status changes to CRIT.
InfluxDB
Sends a webhook
A notification rule posts the status to the HTTP endpoint.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Level crit opens it, ok 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. Add a filter with these values (there is no built-in InfluxDB template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "_level" crit Opens an incident.
Resolve "_level" ok Resolves the open incident.
Match "_check_id" Ties the OK status to the incident it opened.
Title from "_check_name" Becomes the incident title.
Description from "_message" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

To page on warnings too, add a second trigger filter with warn. If one check covers several hosts (grouped by a tag), match on that tag, for example "host".

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

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 the HTTP notification endpoint

  1. In the InfluxDB UI, go to Alerts > Alerts > Notification Endpoints and click Create.
  2. Choose HTTP as the destination, name it Callgoose SQIBS, set the method to POST, authentication to None, and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=influxdb&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 Create Notification Endpoint.

Step 3: Create the notification rule

  1. Go to Notification Rules and click Create. Name it Callgoose SQIBS and choose how often it runs (Schedule Every, for example 1m).
  2. Add the condition When status changes from ANY to CRIT, and a second condition When status changes from ANY to OK, so SQIBS receives the recovery. Use status changes rather than is equal to, or a CRIT check is sent again on every run.
  3. Choose the Callgoose SQIBS endpoint and click Create Notification 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. Lower a check's CRIT threshold for a test.
  2. In SQIBS, a new incident opens. InfluxDB's payload looks like this (shortened):
{
  "_check_id": "0a1b2c3d4e5f6a7b",
  "_check_name": "CPU usage",
  "_level": "crit",
  "_message": "Check: CPU usage is: crit",
  "_notification_rule_name": "Callgoose SQIBS",
  "_source_measurement": "cpu",
  "_time": "2026-11-22T10:15:00Z",
  "_type": "threshold",
  "host": "app-01"
}
  1. Set the threshold back. The rule sends "_level": "ok" for the same check, 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 notification endpoint.

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 an InfluxDB check reports high CPU on a host, SQIBS can run a workflow that finds and restarts the runaway process.

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: