Overview

Send Icinga 2 host and service alerts to Callgoose SQIBS. A small notification script posts each problem and recovery to your SQIBS API endpoint. SQIBS opens an incident on a problem and resolves it when the same host or service recovers.

You need
Icinga 2 with access to /etc/icinga2, curl on the Icinga host, and a SQIBS API token
Setup time
About 20 minutes
Result
Icinga problems open SQIBS incidents; recoveries resolve them

How it works

Icinga
Alert fires
A host or service check goes into a problem state.
Icinga
Sends a webhook
A notification command posts JSON with curl.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
PROBLEM opens it, RECOVERY 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 Icinga template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "notification_type" PROBLEM Opens an incident.
Resolve "notification_type" RECOVERY Resolves the open incident.
Match "alert_key" Host, or host!service: ties the recovery to its problem.
Title from "output" Becomes the incident title.
  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: Add the notification script

Save this script as /etc/icinga2/scripts/notify-callgoose.sh, put in your endpoint and token, and make it executable (chmod 750, owned by the Icinga user):

#!/bin/bash
# /etc/icinga2/scripts/notify-callgoose.sh  - posts one Icinga notification to Callgoose SQIBS.
# Values arrive as environment variables (set in the NotificationCommand below).
URL="https://<your-endpoint>/sqibs-api/v1/process?from=icinga&token=<your-token>"
esc() { printf '%s' "$1" | sed 's/\\/\\\\/g; s/"/\\"/g' | tr '\n\r\t' '   '; }
KEY="$HOSTNAME${SERVICENAME:+!$SERVICENAME}"
curl -s -m 20 -X POST "$URL" -H 'Content-Type: application/json' --data-binary @- <<EOF
{
  "notification_type": "$(esc "$NOTIFICATIONTYPE")",
  "alert_key": "$(esc "$KEY")",
  "host": "$(esc "$HOSTNAME")",
  "service": "$(esc "$SERVICENAME")",
  "state": "$(esc "$STATE")",
  "output": "$(esc "$OUTPUT")",
  "time": "$(date -Iseconds)"
}
EOF

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

Step 3: Add the commands and notifications

Add this to a file under /etc/icinga2/conf.d/ (or your zone directory). It defines one command for services and one for hosts, a user to notify, and apply rules for every host with vars.callgoose = true:

object NotificationCommand "callgoose-notify" {
  command = [ "/etc/icinga2/scripts/notify-callgoose.sh" ]
  env = {
    NOTIFICATIONTYPE = "$notification.type$"
    HOSTNAME = "$host.name$"
    SERVICENAME = "$service.name$"
    STATE = "$service.state$"
    OUTPUT = "$service.output$"
  }
}

object NotificationCommand "callgoose-host-notify" {
  command = [ "/etc/icinga2/scripts/notify-callgoose.sh" ]
  env = {
    NOTIFICATIONTYPE = "$notification.type$"
    HOSTNAME = "$host.name$"
    STATE = "$host.state$"
    OUTPUT = "$host.output$"
  }
}

object User "callgoose" {
  display_name = "Callgoose SQIBS"
}

apply Notification "callgoose-service" to Service {
  command = "callgoose-notify"
  users = [ "callgoose" ]
  types = [ Problem, Recovery ]
  states = [ OK, Warning, Critical, Unknown ]
  assign where host.vars.callgoose == true
}

apply Notification "callgoose-host" to Host {
  command = "callgoose-host-notify"
  users = [ "callgoose" ]
  types = [ Problem, Recovery ]
  states = [ Up, Down ]
  assign where host.vars.callgoose == true
}

Set vars.callgoose = true on the hosts you want in SQIBS, then check and reload: icinga2 daemon -C && systemctl reload icinga2.

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. Stop a monitored service on a test host, or send a custom notification from Icinga Web.
  2. In SQIBS, a new incident opens, titled with the check output. The payload looks like this:
{
  "notification_type": "PROBLEM",
  "alert_key": "web01!HTTP",
  "host": "web01",
  "service": "HTTP",
  "state": "CRITICAL",
  "output": "connect to address 10.0.0.10 and port 80: Connection refused",
  "time": "2026-11-22T10:05:31+00:00"
}
  1. Start the service again. Icinga sends RECOVERY with the same alert_key, 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 script (run it by hand with the same environment variables).

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 Icinga reports the HTTP check failing on a web server, SQIBS can run a workflow that restarts the web service and rechecks it.

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: