Overview
Send IBM Cloud Monitoring alerts to Callgoose SQIBS. IBM Cloud Monitoring is built on Sysdig, so a webhook notification channel posts the standard Sysdig alert JSON to your SQIBS API endpoint. SQIBS opens an incident when an alert becomes active and resolves it when the alert returns to OK.
How it works
ACTIVE 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
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- Add a filter with these values (there is no built-in IBM Cloud Monitoring 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" |
OK |
Resolves the open incident. |
| Match | "alert"."id" |
Ties the OK message to the incident it opened. | |
| Title from | "alert"."subject" |
Becomes the incident title. | |
| Description from | "alert"."body" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
If an alert is segmented (for example by host), each entity sends its own notification with the same alert.id. Match on "entities".[0]."entity" instead, so each host has its own incident.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 notification channel
- Open the IBM Cloud Monitoring web UI for your instance and go to Settings > Notification Channels. Click Add Notification Channel and choose Webhook.
- Set Channel Name to
Callgoose SQIBSand URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=ibmcloudmonitoring&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.
- Under notification options, turn on notifications when alerts are resolved, so SQIBS receives the OK message.
- Turn on Test notification and save the channel.
Step 3: Use the channel in your alerts
Edit an alert (or create one) and add the Callgoose SQIBS channel under Notify. Save the alert.
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.
- Save the channel with Test notification on, or lower an alert threshold for a test.
- In SQIBS, a new incident opens. The alert JSON looks like this (shortened):
{
"timestamp": 1763806500000000,
"alert": {
"id": 21998727,
"name": "Disk space low",
"severity": 2,
"severityLabel": "Medium",
"subject": "Disk space low on web-01 is Triggered",
"body": "Disk space low on web-01 is Triggered"
},
"state": "ACTIVE",
"resolved": false,
"entities": [
{
"entity": "host.hostName = 'web-01'"
}
]
}
- When the alert clears, the channel sends
"state": "OK"for the same alert, 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 notification channel.
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 IBM Cloud Monitoring reports low disk space on a host, SQIBS can run a workflow that clears old logs and rechecks the space.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.