Overview

Send Papertrail log alerts to Callgoose SQIBS. A saved search alert calls a webhook when new log lines match. SQIBS opens an incident for it, so errors in the logs reach the on-call engineer.

You need
A Papertrail account with a saved search, and a SQIBS API token
Setup time
About 10 minutes
Result
Matching log lines open SQIBS incidents

How it works

Papertrail
Alert fires
New log lines match a saved search.
Papertrail
Sends a webhook
The alert posts the matches to the webhook.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
One incident per alert run.

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 Papertrail template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (none) sqibs-critical The saved search name: opens an incident when that search alerts.
  1. Choose the Priority for these incidents and click Save.

Papertrail posts form data, not JSON, so there are no JSON keys to match. Leave Payload JSON key empty: SQIBS then checks Key value contains against the whole message. Without JSON keys SQIBS cannot take a title from the message or tie a recovery to its incident, so these incidents are closed in SQIBS. Give the saved search a one-word name, for example sqibs-critical, so it is easy to match in the posted text.

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.
  1. In Papertrail, run the search you want to alert on and save it as sqibs-critical.
  2. Open the saved search, choose Create Alert, and pick Webhook.
  3. Set the URL to your SQIBS endpoint, and choose how often Papertrail checks (for example every minute):
https://<your-endpoint>/sqibs-api/v1/process?from=papertrail&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 alert.

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. Write a log line that matches the search, for example with logger.
  2. Within the alert interval, a new incident opens in SQIBS.

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 Papertrail alert.

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 Papertrail matches out-of-memory errors in the logs, SQIBS can run a workflow that restarts the affected service.

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: