Overview

Send Loggly log alerts to Callgoose SQIBS. You add SQIBS as an HTTP alert endpoint, then send any saved-search alert to it. SQIBS opens an incident each time the alert fires.

You need
A Loggly account with permission to manage alerts, and a SQIBS API token
Setup time
About 10 minutes
Result
Loggly alerts open SQIBS incidents

How it works

Loggly
Alert fires
A saved search matches more events than the alert allows.
Loggly
Sends a webhook
Through an HTTP alert 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 name.

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 Loggly. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "alert_name" (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_name" so the incident says which alert fired. Loggly 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 SQIBS as an alert endpoint

  1. In Loggly, go to Alerts > Alert Endpoints and click Add New.
  2. Choose HTTP Endpoint, method POST, and give it a name, for example CallgooseSQIBS.
  3. In the URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=loggly&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 endpoint.

Step 3: Send an alert to the endpoint

In Alerts, add or edit an alert on a saved search, tick Send to an endpoint, choose CallgooseSQIBS, and save.

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. Lower an alert's threshold so the current logs break it.
  2. In SQIBS, a new incident opens. Loggly's payload looks like this (shortened):
{
  "alert_name": "IndexOutOfBounds Exception",
  "edit_alert_link": "https://example.loggly.com/alerts/edit/8188",
  "source_group": "N/A",
  "start_time": "Nov 22 10:00:00",
  "end_time": "Nov 22 10:05:00",
  "search_link": "https://example.loggly.com/search/?terms=",
  "query": "* ",
  "num_hits": 225,
  "recent_hits": [],
  "owner_username": "ops"
}

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 Loggly 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 Loggly sees a burst of out-of-memory errors, SQIBS can run a workflow that restarts the affected service and captures a heap summary first.

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: