Overview
Send Sumo Logic monitor alerts to Callgoose SQIBS. A webhook connection posts each alert, and each recovery, to your SQIBS API endpoint. SQIBS opens an incident when a monitor goes critical or warning and resolves it when the monitor recovers.
How it works
Resolved... trigger type 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.
- In Select Integration Template, choose SumoLogic. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "TriggerType" |
(anything) | Opens an incident. |
- Choose the Priority for these incidents and click Save.
The template only opens incidents, for any trigger type. Keep its trigger and add the resolve values below so recoveries resolve the incident (SQIBS checks the resolve values first, so a recovery never opens a new incident):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "TriggerType" |
Opens an incident (Critical, Warning, Missing Data). | |
| Resolve | "TriggerType" |
Resolved |
Resolves the open incident (ResolvedCritical, ResolvedWarning, ResolvedMissingData). |
| Match | "id" |
The monitor ID: ties the recovery to its alert. | |
| Title from | "title" |
Becomes the incident title. | |
| Description from | "Description" |
Becomes the incident description. |
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 connection in Sumo Logic
- In Sumo Logic, go to Monitoring > Connections (Classic UI: Manage Data > Monitoring > Connections) and click + Add. Choose Webhook.
- Set Name to
CallgooseSQIBSand URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=sumologic&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 Alert Payload, use this JSON:
{
"title": "{{Name}}",
"id": "{{Id}}",
"Description": "{{Description}}",
"MonitorType": "{{MonitorType}}",
"TriggerType": "{{TriggerType}}",
"TriggerCondition": "{{TriggerCondition}}",
"TriggerValue": "{{TriggerValue}}",
"QueryURL": "{{QueryURL}}",
"AlertResponseUrl": "{{AlertResponseUrl}}"
}
- Click Test Connection (it sends the payload text, so SQIBS logs it but the placeholders are not filled in), then Save.
Step 3: Send monitor alerts to the connection
- Open a monitor (Monitoring > Monitors), go to Notifications and add the
CallgooseSQIBSconnection. - Choose the trigger types to send (Critical, Warning, Missing Data) and tick the matching recovery so Sumo Logic sends the resolve message.
- Save the monitor.
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.
- Let a monitor trigger, or lower its threshold for a test.
- In SQIBS, a new incident opens, titled with the monitor name. The payload looks like this:
{
"title": "High 5xx rate on checkout",
"id": "00000000000468D5",
"Description": "More than 50 5xx responses in 5 minutes",
"MonitorType": "Logs",
"TriggerType": "Critical",
"TriggerCondition": "Greater than 50",
"TriggerValue": "73",
"QueryURL": "https://service.sumologic.com/ui/#/search/...",
"AlertResponseUrl": "https://service.sumologic.com/ui/#/alert/..."
}
- When the monitor recovers, Sumo Logic sends
"TriggerType": "ResolvedCritical"with the sameid, 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 Sumo Logic connection.
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 a Sumo Logic monitor sees a spike of 5xx errors, SQIBS can run a workflow that restarts the failing application instances.
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.