Overview

Send Logz.io log and metric alerts to Callgoose SQIBS. You add SQIBS as a custom notification endpoint with a small JSON body, then choose it in any alert. SQIBS opens an incident each time the alert triggers.

You need
A Logz.io account with permission to manage notification endpoints, and a SQIBS API token
Setup time
About 10 minutes
Result
Logz.io alerts open SQIBS incidents

How it works

Logz.io
Alert fires
An alert's query crosses its threshold.
Logz.io
Sends a webhook
Through a custom notification endpoint, as JSON.
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 alert title.

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

The template sets no title. Set Incident title from to "alert_title" and Incident description from to "alert_description". Logz.io sends nothing when an alert clears, so close these incidents in SQIBS.

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 a custom notification endpoint

  1. In Logz.io, open the Notification endpoints page and click Add endpoint. Choose the Custom type and name it CallgooseSQIBS.
  2. Set Method to POST, add the header Content-Type=application/json, and set the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=logzio&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. Use this body (the old version of this page had a trailing comma, which is not valid JSON):
{
  "alert_title": "{{alert_title}}",
  "alert_description": "{{alert_description}}",
  "alert_severity": "{{alert_severity}}",
  "alert_event_samples": "{{alert_samples}}"
}
  1. Click Run the test to send a test message, then save the endpoint.

Step 3: Use the endpoint in an alert

Create or edit an alert, and in its notification settings choose the CallgooseSQIBS endpoint. Save the alert.

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. Click Run the test on the endpoint, or let an alert trigger.
  2. In SQIBS, a new incident opens. The payload looks like this (shortened):
{
  "alert_title": "5xx errors on shop-api",
  "alert_description": "More than 50 5xx responses in 5 minutes",
  "alert_severity": "HIGH",
  "alert_event_samples": "[...]"
}

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 Logz.io endpoint.

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 Logz.io reports a spike of 5xx responses, 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: