Overview

Send ScienceLogic SL1 events to Callgoose SQIBS. Two Run Book actions post to your SQIBS API endpoint: one when an event is raised and one when it clears. SQIBS opens an incident on the first and resolves it on the second.

You need
ScienceLogic SL1 with permission to manage Run Book Automation, and a SQIBS API token
Setup time
About 20 minutes
Result
SL1 events open and resolve SQIBS incidents

How it works

ScienceLogic
Alert fires
An event is raised on a device.
ScienceLogic
Sends a webhook
A Run Book action posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
active opens it, cleared 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 ScienceLogic template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "state" active Opens an incident.
Resolve "state" cleared Resolves the open incident.
Match "event_id" Ties the resolve message to the incident it opened.
Title from "message" Becomes the incident title.
Description from "device" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

These values follow the payload shown in the test step. Send one test notification first and confirm the keys with the JSON key creator: SL1 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: Create two Run Book actions

  1. In SL1, go to Registry > Run Book > Actions and create an action that sends an HTTP request (POST, content type application/json) to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=sciencelogic&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. Name it Callgoose SQIBS - Raised and use this body. SL1 replaces the % substitution variables with the event's values:
{
  "event_id": "%e",
  "state": "active",
  "severity": "%S",
  "device": "%X",
  "message": "%M"
}
  1. Create a second action, Callgoose SQIBS - Cleared, with the same body but "state": "cleared".

Step 3: Create two Run Book policies

  1. Go to Registry > Run Book > Automation and create a policy that runs on Event raised for the severities you want (for example Major and Critical) with the Raised action.
  2. Create a second policy that runs when the event is cleared, with the Cleared action.
  3. Enable both policies.

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. Raise a test event on a device, for example by lowering a threshold.
  2. In SQIBS, a new incident opens, titled with the event message.
  3. When SL1 clears the event, the cleared action sends "state": "cleared" for the same event_id, 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 Run Book action.

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 SL1 raises a high-memory event on a server, SQIBS can run a workflow that restarts the service using the most memory.

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: