Overview
Send Graylog alerts to Callgoose SQIBS. An HTTP notification posts each event from your event definitions to your SQIBS API endpoint as JSON. SQIBS opens an incident titled with the event definition.
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 Graylog template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "event_definition_title" |
Opens an incident for every event. | |
| Match | "event_definition_id" |
Groups repeats of the same event definition. | |
| Title from | "event_definition_title" |
Becomes the incident title. | |
| Description from | "event"."message" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
Graylog events have no resolved state, so close the incident in SQIBS once the cause is fixed. To open incidents for some definitions only, put part of their title in Key value contains.
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 an HTTP notification in Graylog
- If your Graylog uses a URL allowlist (System > Configurations), add your SQIBS endpoint to it.
- Go to Alerts > Notifications and click Create Notification. Choose HTTP Notification.
- In URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=graylog&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 Execute Test Notification, then Create.
- Go to Alerts > Event Definitions, edit the definitions you want, and add the notification on the Notifications step.
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.
- Click Execute Test Notification, or let an event definition fire.
- In SQIBS, a new incident opens. Graylog's payload looks like this (shortened):
{
"event_definition_id": "6748e1d2f1c9a2b3c4d5e6f7",
"event_definition_type": "aggregation-v1",
"event_definition_title": "Too many failed logins",
"event_definition_description": "More than 50 failed logins in 5 minutes",
"event": {
"id": "01JDXY7Q8W3K",
"timestamp": "2026-11-22T10:15:00.000Z",
"message": "Too many failed logins: count()=72",
"source": "graylog-1",
"priority": 2,
"alert": true
},
"backlog": []
}
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 Graylog 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 Graylog reports a burst of failed logins from one address, SQIBS can run a workflow that blocks the address on the firewall for an hour.
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.