Overview

Send Hyperping uptime alerts to Callgoose SQIBS. A webhook integration posts a check.down event when a monitor fails and check.up when it recovers. SQIBS opens and resolves the incident to match.

You need
A Hyperping account, and a SQIBS API token
Setup time
About 5 minutes
Result
Hyperping monitors open and resolve SQIBS incidents

How it works

Hyperping
Alert fires
A monitor detects downtime.
Hyperping
Sends a webhook
Through a webhook integration, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
check.down opens it, check.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 Hyperping. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "check"."down" true Opens an incident.
Resolve "check"."down" false Resolves the open incident.
Match "check"."monitorUuid" Ties the resolve message to the incident it opened.
Title from "event" Becomes the incident title.
Description from "text" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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: Add a webhook integration in Hyperping

  1. In Hyperping, go to Integrations and choose Webhook. Give it a name, for example CallgooseSQIBS.
  2. In the endpoint field, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=hyperping&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. Click Create, and make sure your monitors send alerts to this integration.

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. Point a test monitor at an address that returns an error.
  2. In SQIBS, a new incident opens. Hyperping's payload looks like this (shortened):
{
  "event": "check.down",
  "text": "[DOWN] Outage shop-api has started.",
  "check": {
    "url": "https://api.example.com/health",
    "status": 502,
    "down": true,
    "monitorUuid": "mon_jYXcRmK6KCEvDf"
  }
}
  1. When the monitor recovers, Hyperping sends check.up with "down": false for the same monitorUuid, 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 Hyperping integration.

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 Hyperping reports an API down, SQIBS can run a workflow that restarts the API service and checks the health endpoint.

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: