Overview

Send ServiceNow Cloud Observability alerts to Callgoose SQIBS. Cloud Observability (formerly Lightstep) posts each alert to your SQIBS API endpoint through a webhook notification destination. SQIBS opens an incident when an alert fires and resolves it when it clears.

You need
ServiceNow Cloud Observability with permission to manage alerts, and a SQIBS API token
Setup time
About 10 minutes
Result
Alerts open and resolve SQIBS incidents

How it works

ServiceNow Cloud Observability
Alert fires
An alert threshold is crossed.
ServiceNow Cloud Observability
Sends a webhook
Through a webhook destination, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
A critical or warning status opens it, OK 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 ServiceNow Cloud Observability template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" CRITICAL Opens an incident.
Resolve "status" OK Resolves the open incident.
Match "event"."id" Ties the resolve message to the incident it opened.
Title from "event"."description" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

Add a second filter for WARNING if you also page on warnings. These values follow the payload shown in the test step. Send one test notification first and confirm the keys with the JSON key creator: Cloud Observability can change its payload between versions, and SQIBS matches key names exactly (upper and lower case matter).

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 destination

  1. In Cloud Observability, go to Alerts and open Notification destinations. Add a Webhook destination named Callgoose SQIBS.
  2. Enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=cloudobservability&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. Open each alert that should page through SQIBS and add the Callgoose SQIBS destination. Save.

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. Use the destination's test option, or let an alert fire.
  2. In SQIBS, a new incident opens. Check the payload in the API log and adjust the keys if they differ.
  3. When the alert clears, the OK message for the same event 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 webhook destination.

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 Cloud Observability reports a rising error rate on a service, SQIBS can run a workflow that restarts the failing pods.

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: