Overview

Send New Relic alerts to Callgoose SQIBS. A New Relic workflow sends each alert issue to a SQIBS webhook destination. SQIBS opens an incident when the issue is created and resolves it when the issue closes.

You need
A New Relic account with alerts, and a SQIBS API token
Setup time
About 15 minutes
Result
New Relic issues open and close SQIBS incidents

How it works

New Relic
Alert fires
An alert condition opens an issue.
New Relic
Sends a webhook
A workflow sends it to the SQIBS webhook destination.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
A new issue opens it, a closed issue resolves it.

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 NewRelic. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "trigger" INCIDENT_ADDED Opens an incident.
Resolve "trigger" INCIDENT_CLOSED Resolves the open incident.
Match "id" Ties the resolve message to the incident it opened.
Title from "title" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

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 workflow with a SQIBS webhook

  1. In New Relic, go to Alerts > Workflows and click Add a workflow. Name it CallgooseSQIBS.
  2. In Filter data, choose which issues to send, for example by policy or priority.
  3. In Notify, choose Webhook, then Add a destination:
    • Name: CallgooseSQIBS
    • Endpoint URL:
https://<your-endpoint>/sqibs-api/v1/process?from=newrelic&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. Click Save destination. New Relic shows the webhook payload with a preview. Keep the default payload: it contains the id, title and trigger fields the template uses.
  2. Click Send test notification, then Save message and Activate workflow.

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. Send a test notification from the workflow, or let an alert condition open an issue.
  2. In SQIBS, a new incident opens. The default New Relic payload looks like this (shortened):
{
  "id": "d1b1f3fd-995a-4066-88ab-8ce4f6960654",
  "title": "Memory Used % > 90 for at least 2 minutes on 'web-01'",
  "priority": "CRITICAL",
  "state": "ACTIVATED",
  "trigger": "INCIDENT_ADDED",
  "impactedEntities": [
    "web-01"
  ],
  "alertPolicyNames": [
    "Production"
  ],
  "workflowName": "CallgooseSQIBS"
}
  1. When the issue closes, New Relic sends "trigger": "INCIDENT_CLOSED" with the same id, and SQIBS resolves the incident.

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 New Relic webhook destination.

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 New Relic reports slow responses on an app server, SQIBS can run a workflow that recycles the application pool.

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: