Overview

Send Infraon NMS alerts to Callgoose SQIBS. Configure an Infraon notification that posts JSON to your SQIBS API endpoint, and SQIBS opens an incident for each alert, then resolves it when Infraon reports the device is back to normal.

You need
Infraon NMS with permission to manage notifications, and a SQIBS API token
Setup time
About 15 minutes
Result
Infraon NMS alerts open SQIBS incidents

How it works

Infraon NMS
Alert fires
A device or interface alert is raised.
Infraon NMS
Sends a webhook
A webhook notification posts JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
A problem severity opens it, a clear message 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 Infraon NMS template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger (none) Opens an incident for every alert while you capture the payload.
  1. Choose the Priority for these incidents and click Save.

Infraon NMS does not publish a fixed payload for this, so build the filter from the first real message: send a test, open it in the API log, and copy the keys with the JSON key creator. Then set a trigger on the severity or status field (for example Critical), a resolve on the cleared value, and match on the alert or device ID that is the same in both messages.

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 the webhook in Infraon NMS

  1. In Infraon NMS, open the notification or alert action settings and add a webhook notification.
  2. Set the URL to your SQIBS endpoint and the method to POST:
https://<your-endpoint>/sqibs-api/v1/process?from=infraon&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. If Infraon lets you shape the body, send the alert name, severity, status, device and a unique alert ID as plain JSON keys.
  2. Attach the notification to the alert rules or device groups you want in SQIBS, and send both the alert and its clear.

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. Shut an interface on a test device, or use the notification's test option.
  2. In SQIBS, a new incident opens. Copy its keys into the filter with the JSON key creator.
  3. Bring the interface back and check that the clear message 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 Infraon notification.

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 Infraon reports an interface down on a switch, SQIBS can run a workflow that collects the interface counters and bounces the port.

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: