Overview

Send Amazon OpenSearch Service alerts to Callgoose SQIBS. You add SQIBS as a custom webhook notification channel, then send a monitor's trigger action to it. SQIBS opens an incident each time the trigger fires.

You need
An OpenSearch Service domain (OpenSearch 2.x) with alerting, and a SQIBS API token
Setup time
About 10 minutes
Result
OpenSearch monitor triggers open SQIBS incidents

How it works

OpenSearch
Alert fires
A monitor's trigger condition is met.
OpenSearch
Sends a webhook
The trigger action posts your message to the webhook channel.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident takes its title from the description.

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 Amazon OpenSearch. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "trigger" (anything) Opens an incident.
Title from "description" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

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: Add SQIBS as a notification channel

In OpenSearch 2.0 and later, notification channels replace the old alerting destinations.

  1. Sign in to OpenSearch Dashboards and go to Notifications > Channels. Click Create channel.
  2. Set Name to Callgoose_SQIBS_API and Channel type to Custom webhook.
  3. Define the endpoint by URL and enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=opensearch&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. Add the header Content-Type: application/json, then click Create.

Step 3: Send a monitor's trigger to SQIBS

  1. Go to Alerting > Monitors, and create a monitor or edit an existing one.
  2. In a trigger, add an action named Callgoose_SQIBS_Alerts and choose the Callgoose_SQIBS_API channel.
  3. Set the Message to this JSON (keep each value on one line, or the JSON breaks):
{
  "description": "Monitor {{ctx.monitor.name}} just entered alert status. Please investigate the issue.",
  "trigger": "{{ctx.trigger.name}}",
  "severity": "{{ctx.trigger.severity}}",
  "start": "{{ctx.periodStart}}",
  "end": "{{ctx.periodEnd}}"
}
  1. Save the monitor.

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 Send test message in the trigger action, or let the monitor trigger.
  2. In SQIBS, a new incident opens, titled with the description.

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 OpenSearch channel.

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 OpenSearch monitor sees a spike of 5xx errors in the logs, SQIBS can run a workflow that restarts the failing application pods.

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: