Overview

Send Elastic alerts to Callgoose SQIBS, from Elastic Cloud or your own ELK stack. A webhook connector posts to your SQIBS API endpoint, and each rule gets two actions: one when the alert is active and one when it recovers. SQIBS opens the incident on the first and resolves it on the second.

You need
Kibana with permission to manage rules and connectors, and a SQIBS API token
Setup time
About 15 minutes
Result
Elastic alerts open and resolve SQIBS incidents

How it works

Elastic
Alert fires
A rule's condition is met.
Elastic
Sends a webhook
A rule action posts JSON through the webhook connector.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
active opens it, recovered 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

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose ElasticCloud. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger (none) (anything) No key, so every message opens an incident.
  1. Choose the Priority for these incidents and click Save.

The template has no key, so every message opens an incident. With the two actions in step 3, use these values instead:

Part Payload JSON key Key value contains What it does
Trigger "state" active Opens an incident.
Resolve "state" recovered Resolves the open incident.
Match "alert_id" Ties the recovery to the incident it opened.
Title from "rule_name" Becomes the incident title.
Description from "reason" Becomes the incident description.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

Find the right key with the JSON key creator
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: Create a webhook connector

  1. In Kibana, go to Stack Management > Connectors (or search for Connectors) and click Create connector. Choose Webhook.
  2. Name it Callgoose SQIBS, set Method to POST and URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=elastic&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.

  1. Set Authentication to none, and add the HTTP header Content-Type: application/json (Elastic does not send JSON as the content type by default).
  2. Save the connector.

Step 3: Add two actions to each rule

  1. Open the rule (Stack Management > Rules, or Observability > Alerts > Manage rules) and add an action with the Callgoose SQIBS connector. Run it when the alert is active (the rule's main action group), and use this body:
{
  "state": "active",
  "alert_id": "{{alert.uuid}}",
  "rule_name": "{{rule.name}}",
  "rule_id": "{{rule.id}}",
  "reason": "{{context.reason}}",
  "date": "{{date}}",
  "kibana_url": "{{kibanaBaseUrl}}"
}
  1. Add a second action with the same connector that runs when the alert is Recovered, with the same body but "state": "recovered".
  2. Save the rule.

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.

  1. Use Test on the connector to send a sample body, or let the rule fire.
  2. In SQIBS, a new incident opens, titled with the rule name.
  3. When the alert recovers, the second action sends "state": "recovered" with the same alert_id, 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 Elastic connector.

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 an Elastic rule finds an error spike in an application's logs, SQIBS can run a workflow that restarts the application and checks the error rate again.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

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:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. 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: