Overview
Send Coralogix alerts to Callgoose SQIBS. A generic outbound webhook posts each alert to your SQIBS API endpoint. SQIBS opens an incident when an alert triggers and resolves it when Coralogix resolves the alert.
How it works
trigger opens it, resolve 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 Coralogix. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "alert_action" |
trigger |
Opens an incident. |
| Resolve | "alert_action" |
resolve |
Resolves the open incident. |
| Match | "alert_url" |
Ties the resolve message to the incident it opened. | |
| Title from | "description" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
The template matches on "alert_url", which is the same for every firing of one alert definition. With the body below, change Map incident with (trigger and resolve) to "dedup_key": Coralogix keeps it the same from trigger to resolve and changes it for the next firing.
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 an outbound webhook in Coralogix
- In Coralogix, open the outbound webhooks page (Integrations > Outbound webhooks) and add a Generic webhook.
- Set the name to
CallgooseSQIBS, the method to POST, and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=coralogix&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.
- Edit the body and use this JSON. Every value is quoted, so the JSON stays valid even when a placeholder is empty:
{
"dedup_key": "$RESOLVED_AWARE_DEDUP_KEY",
"alert_id": "$ALERT_ID",
"name": "$ALERT_NAME",
"description": "$ALERT_DESCRIPTION",
"event_severity": "$EVENT_SEVERITY",
"threshold": "$ALERT_THRESHOLD",
"timewindow": "$ALERT_TIMEWINDOW_MINUTES",
"group_by_labels": "$ALERT_GROUPBY_LABELS",
"alert_action": "$ALERT_ACTION",
"alert_url": "$ALERT_URL",
"log_url": "$LOG_URL",
"service": "$SERVICE",
"duration": "$DURATION",
"errors": "$ERRORS"
}
- Click TEST CONFIG, then save.
Step 3: Use the webhook in your alerts
In each alert definition, add CallgooseSQIBS under notifications, and make sure it notifies on resolve as well as on trigger.
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.
- Click TEST CONFIG, or let an alert trigger.
- In SQIBS, a new incident opens, titled with the alert description. The payload looks like this (shortened):
{
"dedup_key": "c1f7d3a9e2b44d1f",
"alert_id": "8b2f1c3d",
"name": "Checkout errors",
"description": "More than 50 checkout errors in 5 minutes",
"event_severity": "Critical",
"alert_action": "trigger",
"alert_url": "https://example.coralogix.com/#/insights?id=8b2f1c3d",
"service": "checkout"
}
- When the alert resolves, Coralogix sends
"alert_action": "resolve"with the samededup_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 Coralogix 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 Coralogix sees a burst of errors from one service, SQIBS can run a workflow that restarts that service's containers.
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.