Overview

Send PRTG sensor alerts to Callgoose SQIBS. Two notification templates run a small PowerShell script that posts JSON to your SQIBS API endpoint: one when a sensor goes down, one when the condition clears. SQIBS opens the incident on the first and resolves it on the second.

You need
PRTG Network Monitor (on-premises) with admin access, and a SQIBS API token
Setup time
About 20 minutes
Result
PRTG sensors open and resolve SQIBS incidents

How it works

PRTG
Alert fires
A sensor goes into the Down state.
PRTG
Sends a webhook
A notification runs a script that posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
down opens it, up 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 PRTG template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "event" up Resolves the open incident.
Trigger "event" down Opens an incident.
Match "sensorid" The PRTG sensor ID: ties the up message to its incident.
Title from "sensor" 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.

Why a script

PRTG's Execute HTTP Action can only post form data (application/x-www-form-urlencoded), not JSON. The script sends proper JSON, with a fixed event value per template, so a status text such as Up (was: Down) can never be mistaken for a new problem.

Step 2: Add the script and two notification templates

  1. Save this script as Callgoose-SQIBS.ps1 in the Notifications\EXE folder of the PRTG program directory on the core server:
# Callgoose-SQIBS.ps1 - put it in the PRTG "Notifications\EXE" folder on the core server
param([string]$Event, [string]$SensorId, [string]$Device, [string]$Sensor, [string]$Status, [string]$Message, [string]$Link)
$body = @{ event = $Event; sensorid = $SensorId; device = $Device; sensor = $Sensor;
           status = $Status; message = $Message; link = $Link } | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri 'https://<your-endpoint>/sqibs-api/v1/process?from=prtg' `
  -Headers @{ Authorization = 'Bearer <your-token>' } -ContentType 'application/json' -Body $body

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

  1. In PRTG, go to Setup > Account Settings > Notification Templates and add a template Callgoose SQIBS - Down. Turn on Execute Program, choose the script, and set Parameters to:
-Event 'down' -SensorId '%sensorid' -Device '%device' -Sensor '%sensor' -Status '%status' -Message '%message' -Link '%linksensor'
  1. Add a second template, Callgoose SQIBS - Up, with the same settings and -Event 'up'.

Step 3: Add the notification triggers

On a group, device or sensor, open Notification Triggers and add a state trigger: when the sensor is Down for at least 60 seconds, perform Callgoose SQIBS - Down; when the condition clears, perform Callgoose SQIBS - Up. Triggers set on a group are inherited by everything in it.

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. In the template list, use Send Test Notification on Callgoose SQIBS - Down, or pause a test service so its sensor goes down.
  2. In SQIBS, a new incident opens, titled with the sensor name.
  3. When the sensor is up again, the Up template runs, 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.

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 PRTG reports a Windows service sensor down, SQIBS can run a PowerShell workflow that starts the service again.

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: