Overview

Send PingPlotter alerts to Callgoose SQIBS. Two webhook actions on a PingPlotter alert post JSON to your SQIBS API endpoint: one when the alert condition starts, one when it ends. SQIBS opens an incident on the first and resolves it on the second.

You need
PingPlotter (Standard, Professional or Cloud) with alerts, and a SQIBS API token
Setup time
About 10 minutes
Result
PingPlotter alerts open and resolve SQIBS incidents

How it works

PingPlotter
Alert fires
Latency or packet loss to a target breaks the alert condition.
PingPlotter
Sends a webhook
A webhook action posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Started opens it, Ended 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 PingPlotter template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "event_state" Ended Resolves the open incident.
Trigger "event_state" Started Opens an incident.
Match "alert_key" Alert and target: ties the end event to its start.
Title from "alert_name" Becomes the incident title.
Description from "description" 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: Add webhook actions to a PingPlotter alert

  1. In PingPlotter, go to Alerts and create an alert, for example latency over 200 ms for 10 samples.
  2. Add an action of type webhook (send to URL) for the start of the alert, with method POST and your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=pingplotter&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. Use this body for the start action:
{
  "event_state": "Started",
  "alert_key": "{{AlertName}}-{{Host.HostName}}",
  "alert_name": "{{AlertName}}",
  "target": "{{Host.HostName}}",
  "agent": "{{AgentName}}",
  "description": "Alert started for target {{Host.HostName}}"
}
  1. Add a second action for the end of the alert with the same body and "event_state": "Ended".
  2. Apply the alert to the targets you want in SQIBS.

Step 3: 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. Apply the alert to a target that does not answer.
  2. In SQIBS, a new incident opens, titled with the alert name.
  3. Point the target back at a healthy address. The end action sends Ended for 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 PingPlotter alert 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 PingPlotter reports packet loss to a branch office, SQIBS can run a workflow that collects a traceroute and the router's interface errors for the engineer.

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: