Overview
Send Motadata alerts to Callgoose SQIBS. A webhook alert (NMS) or a Send HTTP Request action (AIOps, ServiceOps) posts each alert to your SQIBS API endpoint as JSON. SQIBS opens an incident for a problem and resolves it when Motadata reports the alert clear.
How it works
clear 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 Motadata template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Resolve | "status" |
clear |
Resolves the open incident. |
| Trigger | "status" |
Opens an incident for every other state (critical, major, warning). | |
| Match | "alert_key" |
Device plus rule: ties the clear message to its incident. | |
| Title from | "rule_name" |
Becomes the incident title. | |
| Description from | "description" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
SQIBS checks the Resolve filter before the Trigger filter, so a Trigger with no value opens an incident for every other message (any problem state) while recoveries resolve. Use the word your Motadata version sends for a cleared alert (for example clear or ok).
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 the webhook in Motadata
- In Motadata NMS, open the webhook alert settings; in AIOps or ServiceOps, add a Send HTTP Request action to an automation workflow.
- Set Method to POST, Content-Type to
application/json, and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=motadata&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.
- Use this body. The variable names differ between Motadata products and versions, so pick the matching ones from the variable list next to the body field:
{
"status": "${ALERT_STATUS}",
"alert_key": "${DEVICE}-${RULE_NAME}",
"rule_name": "${RULE_NAME}",
"severity": "${SEVERITY}",
"device": "${DEVICE}",
"description": "Value ${METRIC_VALUE}, threshold ${THRESHOLD}",
"url": "${ALERT_URL}"
}
- Attach the notification to the alert rules (NMS) or save the workflow (AIOps, ServiceOps).
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.
- Lower a threshold for a test so an alert fires, or use the test option on the notification.
- In SQIBS, a new incident opens, titled with the rule name.
- Restore the threshold. Motadata sends the clear state for the same
alert_key, 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 Motadata notification.
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 Motadata reports high CPU on a server, SQIBS can run a workflow that collects the top processes and restarts the runaway service.
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.