Overview

Send BMC TrueSight Operations Management (now BMC Helix Operations Management) events to Callgoose SQIBS. An event policy forwards matching events to your SQIBS API endpoint. SQIBS opens an incident for an open critical event and resolves it when the event closes.

You need
BMC TrueSight or Helix Operations Management with permission to create event policies, and a SQIBS API token
Setup time
About 20 minutes
Result
TrueSight events open and resolve SQIBS incidents

How it works

TrueSight
Alert fires
A critical event opens on a monitored device.
TrueSight
Sends a webhook
An event policy posts the event as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
OPEN opens it, CLOSED 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 TrueSight template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "status" OPEN Opens an incident.
Resolve "status" CLOSED Resolves the open incident.
Match "mc_ueid" The event's unique id ties the close to its incident.
Title from "msg" Becomes the incident title.
Description from "mc_host" The host becomes the description.
  1. Choose the Priority for these incidents and click Save.

The menu names and field names differ between TrueSight and Helix versions. Use the values above as a starting point and confirm them from your first test message.

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: Forward events from TrueSight

  1. In the TrueSight console (or BMC Helix Operations Management), open Configuration > Event Management Policies and create a policy.
  2. Choose a notification or webhook action that sends JSON to a URL, and enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=truesight&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. Set the event selection criteria (for example severity Critical or Major) and include the event status, message, host and unique id in the body.
  2. Enable the policy so it also runs when events close.

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. Generate a test event that matches the policy.
  2. In SQIBS, a new incident opens. The payload below shows the shape to expect. Field names can differ between versions, so send one test message first and copy the exact keys from the API log with the JSON key creator.
{
  "status": "OPEN",
  "severity": "CRITICAL",
  "msg": "Disk /var is 97% full",
  "mc_host": "db-prod-1",
  "mc_ueid": "mc.pncell_bmcts.5f3a2b1c.123"
}
  1. Close the event; 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 event policy.

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 TrueSight reports a full file system, SQIBS can run a workflow that clears old logs and closes the event once space is back.

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: