Overview

Send Komodor Kubernetes alerts to Callgoose SQIBS. A Komodor real-time health monitor sends its notifications to a webhook channel pointed at your SQIBS API endpoint, and SQIBS opens an incident for each alert.

You need
Komodor with permission to edit monitors, and a SQIBS API token
Setup time
About 10 minutes
Result
Komodor monitor alerts open SQIBS incidents

How it works

Komodor
Alert fires
A real-time health monitor detects a problem.
Komodor
Sends a webhook
Through a webhook channel, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
The incident opens for each alert.

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. Add a filter with these values (there is no built-in Komodor template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (none) Opens an incident for every alert while you capture the payload.
  1. Choose the Priority for these incidents and click Save.

Komodor does not publish a fixed payload for this, so build the filter from the first real message: send a test, open it in the API log, and copy the keys with the JSON key creator. Then match on the workload or service identifier so repeated alerts for the same workload stay in one incident, and add a resolve filter if Komodor sends a resolved state.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

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 the webhook in Komodor

  1. In Komodor, open Realtime Health Monitors, choose the cluster and the monitor you want in SQIBS.
  2. In the monitor's notification settings, choose Webhook. Create a channel if you have none yet, with your SQIBS endpoint as the Webhook URL:
https://<your-endpoint>/sqibs-api/v1/process?from=komodor&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. Save the monitor. Repeat for other monitors (availability, node, job, and so on).

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.

  1. Deploy a test workload that crash-loops on a test cluster.
  2. In SQIBS, a new incident opens. Copy its keys into the filter with the JSON key creator.

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 Komodor 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 Komodor reports a deployment with pods in CrashLoopBackOff, SQIBS can run a kubectl workflow that collects the logs and rolls the deployment back.

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: