Overview

Send Zabbix problems to Callgoose SQIBS. A webhook media type posts each problem and recovery to your SQIBS API endpoint, and a trigger action uses it. SQIBS opens an incident when a problem starts and resolves it when Zabbix reports the recovery.

You need
Zabbix 6.0 or later with admin access, and a SQIBS API token
Setup time
About 20 minutes
Result
Zabbix problems open SQIBS incidents; recoveries resolve them

How it works

Zabbix
Alert fires
A trigger goes into the problem state.
Zabbix
Sends a webhook
A webhook media type posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
PROBLEM opens it, RESOLVED 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 Zabbix template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "event_status" PROBLEM Opens an incident.
Resolve "event_status" RESOLVED Resolves the open incident.
Match "event_id" Zabbix sends the problem's event id in the recovery too.
Title from "subject" Becomes the incident title.
Description from "message" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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 a webhook media type

  1. In Zabbix, go to Alerts > Media types and click Create media type. Set Type to Webhook and Name to Callgoose SQIBS.
  2. Add these Parameters (name = value):
url = https://<your-endpoint>/sqibs-api/v1/process?from=zabbix&token=<your-token>
event_id = {EVENT.ID}
event_value = {EVENT.VALUE}
event_status = {EVENT.STATUS}
severity = {EVENT.SEVERITY}
host = {HOST.NAME}
subject = {ALERT.SUBJECT}
message = {ALERT.MESSAGE}

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Paste this Script:
var params = JSON.parse(value);
var req = new HttpRequest();
req.addHeader('Content-Type: application/json');
var resp = req.post(params.url, JSON.stringify({
  event_id: params.event_id,
  event_value: params.event_value,
  event_status: params.event_status,
  severity: params.severity,
  host: params.host,
  subject: params.subject,
  message: params.message
}));
if (req.getStatus() != 200) { throw 'SQIBS returned HTTP ' + req.getStatus(); }
return 'OK';
  1. Click Add. Use Test on the media type to send a sample.

Step 3: Send problems and recoveries to SQIBS

  1. Go to Users > Users, open a user for the integration (for example callgoose), and on the Media tab add the Callgoose SQIBS media type with any send-to value.
  2. Go to Alerts > Actions > Trigger actions and create an action (or edit one). Set the conditions, for example severity at least High.
  3. On Operations, send a message to the integration user through Callgoose SQIBS. Add the same under Recovery operations so incidents resolve.
  4. Click Add.

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 Test on the media type, or let a trigger fire on a test host.
  2. In SQIBS, a new incident opens, titled with the alert subject.
  3. When the problem recovers, Zabbix sends "event_status": "RESOLVED" with the same event_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 media type.

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 Zabbix reports a service down on a host, SQIBS can run a workflow that restarts it over SSH and rechecks.

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: