Overview
Send Lumigo alerts to Callgoose SQIBS. A Lumigo webhook integration posts each alert to your SQIBS API endpoint, with the issue and the affected resource. SQIBS opens an incident for each issue.
How it works
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 Lumigo template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "issue"."level" |
error |
Opens an incident for error-level issues. |
| Match | "issue"."id" |
Keeps repeated alerts of one issue together. | |
| Title from | "issue"."type" |
Becomes the incident title. | |
| Description from | "issue"."message" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
Lumigo levels are error, warning and insight; add a filter for warning if you page on those too. The payload also carries issue.state; if your alerts send a resolved state, add a resolve filter on it with the same match.
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 Lumigo
- In Lumigo, open the project's sidebar and go to Settings > Integrations. Under Webhooks, click Integrate.
- Enter a name, for example
Callgoose SQIBS, and your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=lumigo&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.
- Click Save.
Step 3: Send alerts to the webhook
Click Alerts, create or edit an alert, select Webhooks as the notification service, set the notification preferences, and click Save 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.
- Invoke a test function that throws an error.
- In SQIBS, a new incident opens. Lumigo's payload looks like this (shortened):
{
"lumigoProject": {
"id": "p-1234",
"name": "shop"
},
"issue": {
"id": "a1b2c3d4",
"level": "error",
"type": "Runtime Error",
"state": "active",
"message": "TypeError: Cannot read properties of undefined (reading 'total')",
"lastOccurrenceTimestamp": 1763806500000
},
"resource": {
"id": "arn:aws:lambda:ap-southeast-1:123456789012:function:checkout",
"type": "function",
"name": "checkout",
"region": "ap-southeast-1",
"runtime": "nodejs20.x"
}
}
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 Lumigo webhook.
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 Lumigo reports timeouts on a function after a release, SQIBS can run a workflow that shifts the function alias back to the previous version.
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.