Overview

Send AdRem NetCrunch alerts to Callgoose SQIBS. A webhook action in a NetCrunch alerting script posts each alert to your SQIBS API endpoint as JSON. SQIBS opens an incident when an alert starts and resolves it when NetCrunch reports it closed.

You need
AdRem NetCrunch with permission to edit alerting scripts, and a SQIBS API token
Setup time
About 15 minutes
Result
NetCrunch alerts open and resolve SQIBS incidents

How it works

NetCrunch
Alert fires
A node, service or performance alert starts.
NetCrunch
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
ALERT opens it, OK closes 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. Add a filter with these values (there is no built-in NetCrunch template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "status" OK Resolves the open incident.
Trigger "status" ALERT Opens an incident.
Match "alert_id" Ties the closing message to the incident it opened.
Title from "title" Becomes the incident title.
Description from "description" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

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.

Step 2: Add a webhook action in NetCrunch

  1. In the NetCrunch console, open the alerting scripts (notification policies) used by the nodes you want in SQIBS.
  2. Add an action of type Webhook with Method POST, Content-Type application/json, and the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=netcrunch&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. Check each placeholder against the variable list in the webhook editor of your NetCrunch version:
{
  "alert_id": "{AlertId}",
  "node_name": "{NodeName}",
  "ip_address": "{IpAddress}",
  "status": "{Status}",
  "severity": "{Severity}",
  "title": "{AlertName}",
  "description": "{Description}",
  "timestamp": "{EventTime}"
}
  1. Add the same action to the alert's closing (end of alert) step, so SQIBS hears when it is over. Save the script.

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. Stop a test service on a monitored node.
  2. In SQIBS, a new incident opens, titled with the alert name.
  3. Start the service again. NetCrunch sends "status": "OK" for the same alert_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 NetCrunch webhook 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 NetCrunch reports a Windows service stopped, SQIBS can run a PowerShell workflow that starts it again.

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: