Overview
Send Enginsight alerts to Callgoose SQIBS. A webhook posts each alert and its resolution to your SQIBS API endpoint. SQIBS opens an incident when an alert is raised and resolves it when Enginsight reports it resolved.
How it works
resolved: false opens it, true 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 Enginsight. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "resolved" |
false |
Opens an incident. |
| Resolve | "resolved" |
true |
Resolves the open incident. |
| Match | "alert"."_id" |
Ties the resolve message to the incident it opened. | |
| Title from | "alert"."name" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template matches on the alert definition ("alert"."_id"), so one alert shared by many endpoints shares one incident. To track each endpoint on its own, create one alert per endpoint.
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 in Enginsight
- In Enginsight, go to Alerts > Webhooks and click Create webhook.
- Give it a name and enter your SQIBS endpoint as the Target URL:
https://<your-endpoint>/sqibs-api/v1/process?from=enginsight&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.
- Set Method to POST and Content-Type to
application/json, then click Add webhook.
Step 3: Create an alert that uses the webhook
- In Alerts > Overview, click Create alert.
- Choose the kind of alert (for example Endpoint), the reference (by tags or specific endpoints), the metric and the threshold.
- Under notifications, choose the webhook from step 2, and save.
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.
- Set a threshold the endpoint already breaks, for example a response time above 100 ms.
- In SQIBS, a new incident opens, titled with the alert name. Enginsight's payload looks like this (shortened):
{
"resolved": false,
"belongsTo": "endpoint",
"alert": {
"name": "Response time",
"_id": "67638d4505e30815710edde2"
},
"createdAt": "2026-11-22T03:15:57.064Z",
"scenario": {
"payload": [
{
"triggered": true,
"value": "7749.00",
"threshold": "100",
"operator": "gt",
"property": "endpoints_websites.website.total"
}
]
}
}
- When the value is back under the threshold, Enginsight sends
"resolved": truefor 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 Enginsight 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 Enginsight reports a host running out of memory, SQIBS can run a workflow that restarts the service using the most memory.
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.