Overview

Send SolarWinds Platform (Orion) alerts to Callgoose SQIBS. An alert definition gets two actions that post JSON to your SQIBS API endpoint: a trigger action when the alert fires and a reset action when it clears. SQIBS opens the incident on the first and resolves it on the second.

You need
SolarWinds Platform (Orion) with permission to manage alerts, and a SQIBS API token
Setup time
About 20 minutes
Result
SolarWinds alerts open and resolve SQIBS incidents

How it works

SolarWinds
Alert fires
An alert's trigger condition is met.
SolarWinds
Sends a webhook
A trigger action posts JSON over HTTPS.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
triggered opens it, the reset action's 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. In Select Integration Template, choose SolarWinds. 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, resets included. With the actions below, use these values instead:

Part Payload JSON key Key value contains What it does
Trigger "event_type" triggered Opens an incident.
Resolve "event_type" resolved Resolves the open incident.
Match "alert_key" Ties the reset to the alert it belongs to.
Title from "alert_name" Becomes the incident title.
Description from "message" Becomes the incident description.

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 alert and its trigger action

  1. In the SolarWinds Platform web console, go to Alerts & Activity > Alerts > Manage Alerts and click Add New Alert (or edit an alert).
  2. Give it a name and description, keep Enabled on, and set the Trigger Condition and Reset Condition you need.
  3. Under Trigger Actions, click Add Action, choose Send a GET or POST Request to a Web Server and click Configure Action.
  4. Name it CallgooseSQIBS - Triggered.
  5. In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=solarwinds&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. Choose Use HTTP/S POST, set the content type to application/json, and paste this body:
{
  "event_type": "triggered",
  "alert_key": "${N=Alerting;M=AlertObjectID}",
  "alert_name": "${N=Alerting;M=AlertName}",
  "object": "${N=SwisEntity;M=Caption}",
  "message": "${N=Alerting;M=AlertMessage}",
  "severity": "${N=Alerting;M=Severity}",
  "details_url": "${N=Alerting;M=AlertDetailsUrl}"
}
  1. Click Save Changes.

Step 3: Add the reset action

  1. Under Reset Actions, add the same kind of action, named CallgooseSQIBS - Resolved, with the same URL.
  2. Use the same body with "event_type": "resolved":
{
  "event_type": "resolved",
  "alert_key": "${N=Alerting;M=AlertObjectID}",
  "alert_name": "${N=Alerting;M=AlertName}",
  "object": "${N=SwisEntity;M=Caption}",
  "message": "${N=Alerting;M=AlertMessage}",
  "severity": "${N=Alerting;M=Severity}",
  "details_url": "${N=Alerting;M=AlertDetailsUrl}"
}
  1. Save, review the summary and click Submit.

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 Simulate on the trigger action, or let the alert fire.
  2. In SQIBS, a new incident opens, titled with the alert name.
  3. When the reset condition is met, the reset action sends "event_type": "resolved" 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 SolarWinds actions.

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 SolarWinds reports high CPU on a Windows node, SQIBS can run a PowerShell workflow that restarts the runaway service on that node.

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: