Overview

Send Chronosphere alerts to Callgoose SQIBS. A webhook notifier in a notification policy posts each alert to your SQIBS API endpoint in the Prometheus Alertmanager format. SQIBS opens an incident when an alert fires and resolves it when the alert resolves.

You need
A Chronosphere tenant with permission to manage notifiers and policies, and a SQIBS API token
Setup time
About 15 minutes
Result
Chronosphere alerts open and resolve SQIBS incidents

How it works

Chronosphere
Alert fires
A monitor's query breaks its threshold.
Chronosphere
Sends a webhook
A webhook notifier posts the alert group, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Status firing opens it, 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. Add a filter with these values (there is no built-in Chronosphere template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" firing Opens an incident.
Resolve "status" resolved Resolves the open incident.
Match "groupKey" Ties the resolve message to the incident it opened.
Title from "commonAnnotations"."summary" Becomes the incident title.
Description from "commonLabels"."alertname" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

The format is the same as Prometheus Alertmanager; the Prometheus page explains the keys in more detail.

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 a webhook notifier in Chronosphere

  1. In Chronosphere, open Alerts > Notifiers and create a notifier of type Webhook. Name it Callgoose SQIBS.
  2. Enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=chronosphere&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. Make sure resolved notifications are sent, and save.

Step 3: Route alerts to the notifier

Open the notification policy used by your monitors and add the Callgoose SQIBS notifier for the severities you want (for example critical), then save.

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. Make a test monitor fire, for example by lowering its threshold.
  2. In SQIBS, a new incident opens, titled with the alert summary. The payload looks like this (shortened):
{
  "receiver": "Callgoose SQIBS",
  "status": "firing",
  "groupKey": "{}:{alertname=\"HighErrorRate\"}",
  "commonLabels": {
    "alertname": "HighErrorRate",
    "severity": "critical"
  },
  "commonAnnotations": {
    "summary": "Error rate above 5% on checkout"
  },
  "alerts": [
    {
      "status": "firing",
      "labels": {
        "alertname": "HighErrorRate",
        "service": "checkout"
      }
    }
  ]
}
  1. When the alert resolves, the same group sends "status": "resolved" 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 Chronosphere notifier.

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 Chronosphere reports a high error rate on a service, SQIBS can run a workflow that rolls back the last deployment.

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: