Overview

Send Falcon LogScale alerts to Callgoose SQIBS. LogScale is the new name of Humio. A webhook action posts each alert to your SQIBS API endpoint, and SQIBS opens an incident for it.

You need
A LogScale repository where you can manage alerts and actions, and a SQIBS API token
Setup time
About 10 minutes
Result
LogScale alerts open SQIBS incidents

How it works

LogScale
Alert fires
An alert's query finds matching events.
LogScale
Sends a webhook
A webhook action posts 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.

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

LogScale does not send a message when an alert stops matching, so close these incidents in SQIBS when the cause is fixed.

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 action in LogScale

  1. In the repository, open Alerts > Actions and click New action. Name it CallgooseSQIBS and choose Webhook as the action type.
  2. Enter your SQIBS endpoint as the Endpoint URL, set Method to POST, and add the header Content-Type: application/json:
https://<your-endpoint>/sqibs-api/v1/process?from=logscale&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 Message body template. {event_count} and {events} are left unquoted on purpose: LogScale fills them with a number and a JSON array.
{
  "title": "{trigger_type} in LogScale",
  "repository": "{repo_name}",
  "timestamp": "{triggered_timestamp}",
  "alert": {
    "name": "{name}",
    "description": "{description}",
    "id": "{id}",
    "query": {
      "queryString": "{query_string}",
      "start": "{query_time_start}",
      "end": "{query_time_end}"
    }
  },
  "numberOfEvents": {event_count},
  "events": {events}
}
  1. Click Create action, then Test action.

Step 3: Use the action in an alert

Open (or create) an alert on a query, add the CallgooseSQIBS action, and save. Each time the alert fires, SQIBS opens an incident.

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 Test action, or let an alert fire.
  2. In SQIBS, a new incident opens, titled from the title field.
  3. Check the payload in the API log and refine the filter, for example open incidents only for alerts whose name contains prod.

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 LogScale action.

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 a LogScale alert finds repeated failed logins on a server, SQIBS can run a workflow that blocks the source address and collects the auth log.

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: