Overview

Send Alertra monitoring alerts to Callgoose SQIBS. Alertra has no generic webhook, but its Slack integration posts a small JSON message that SQIBS can read. Point it at your SQIBS API endpoint and SQIBS opens an incident when a device goes down.

You need
An Alertra account with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
Alertra down alerts open SQIBS incidents

How it works

Alertra
Alert fires
A monitored device goes down.
Alertra
Sends a webhook
Through a Slack-format webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the alert text.

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 Alertra template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "text" is DOWN Opens an incident.
Title from "text" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

The Slack format has no alert id, so SQIBS cannot tie an OnUp message to its incident. Do not send OnUp to SQIBS (it would not match this filter anyway); close the incident in SQIBS, or let an automation workflow resolve it after its recheck succeeds.

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 the webhook in Alertra

  1. In Alertra, open Settings > Integrations and click Create New Integration.
  2. Choose Slack as the type and give it a name, for example CallgooseSQIBS.
  3. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=alertra&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. Edit the device, and for the OnDown event add the integration. Add OnWarning too if you want warnings in SQIBS (and add a filter for them).

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 device at an address that does not answer, or wait for a real outage.
  2. In SQIBS, a new incident opens, titled with the alert text. Alertra sends payloads like this:
{
  "icon_url": "http://public.alertra.com/img/logo-new.png",
  "text": "Device shop-web is DOWN: HTTP status code does not match 200 (503)",
  "username": "Alertra"
}

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 Alertra 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 Alertra reports a site down, SQIBS can run a workflow that restarts the web server and rechecks the page.

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: