Overview

Send WhatsUp Gold device alerts to Callgoose SQIBS. A PowerShell script action posts the device and its state to your SQIBS API endpoint, and an action policy runs it when a device goes down and when it comes back up. SQIBS opens and resolves the incident to match.

You need
WhatsUp Gold with permission to manage actions and policies, and a SQIBS API token
Setup time
About 20 minutes
Result
WhatsUp Gold devices open and resolve SQIBS incidents

How it works

WhatsUp Gold
Alert fires
A device goes down.
WhatsUp Gold
Sends a webhook
An action policy runs a PowerShell 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. In Select Integration Template, choose Progress WhatsUpGold. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger (none) (anything) No key, so every message opens an incident.
  1. Choose the Priority for these incidents and click Save.

The template has no key, so every message opens an incident. With the script below, use these values instead:

Part Payload JSON key Key value contains What it does
Trigger "Device State" Down Opens an incident.
Resolve "Device State" Up Resolves the open incident.
Match "Device ID" Ties the up message to the incident its down message opened.
Title from "Alert message" Becomes the incident title.

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: Create the PowerShell script action

  1. In WhatsUp Gold, go to Actions and Policies > Actions, click Add and choose the PowerShell Script action type.
  2. Name it Callgoose SQIBS and paste this script, with your endpoint and token:
$headers = @{
  'Content-Type'  = 'application/json'
  'Authorization' = 'Bearer <your-token>'
}
$body = @{
  'Device'       = '%Device.DisplayName'
  'Device ID'    = '%Device.DatabaseID'
  'Device State' = '%Device.State'
  'Address'      = '%Device.Address'
  'Alert message' = '%Device.DisplayName is %Device.State (%Device.Address)'
  'Monitors down' = '%Device.ActiveMonitorDownNames'
  'Monitors up'   = '%Device.ActiveMonitorUpNames'
}
Invoke-RestMethod -Method Post -Uri 'https://<your-endpoint>/sqibs-api/v1/process?from=whatsupgold' `
  -Headers $headers -Body ($body | ConvertTo-Json) -ContentType 'application/json'

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

  1. Save the action.

Step 3: Run it from an action policy

  1. Go to Action Policies and create a policy, for example Callgoose SQIBS.
  2. Add the Callgoose SQIBS action twice: once for the device Down state and once for Up.
  3. Assign the policy to the devices (or device groups) you want in SQIBS.

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 the action's test option, or stop a test device's monitored service.
  2. In SQIBS, a new incident opens. The payload looks like this:
{
  "Device": "core-switch-01",
  "Device ID": "1042",
  "Device State": "Down",
  "Address": "10.0.0.2",
  "Alert message": "core-switch-01 is Down (10.0.0.2)",
  "Monitors down": "Ping, SNMP",
  "Monitors up": ""
}
  1. When the device is up again, the policy sends "Device State": "Up" for the same device 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 PowerShell action.

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 WhatsUp Gold reports a Windows service monitor down, SQIBS can run a PowerShell workflow that restarts the service on that server.

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: