Overview

Send NetApp Data Infrastructure Insights alerts to Callgoose SQIBS. The product was called Cloud Insights until 2024. A generic webhook posts each monitor alert to your SQIBS API endpoint. SQIBS opens an incident for critical and warning alerts and resolves it when the alert is resolved.

You need
Data Infrastructure Insights with admin access, and a SQIBS API token
Setup time
About 15 minutes
Result
Storage and infrastructure alerts open and resolve SQIBS incidents

How it works

NetApp
Alert fires
A monitor's condition is met.
NetApp
Sends a webhook
Through a generic webhook, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
Critical or warning opens it, Resolved 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 NetApp Data Infrastructure Insights template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Resolve "severity" resolved Resolves the open incident.
Trigger "severity" Opens an incident for critical and warning alerts.
Match "alertId" Ties the resolved message to the incident it opened.
Title from "monitorName" Becomes the incident title.
Description from "alertDescription" Becomes the incident description.
  1. Choose the Priority for these incidents and click Save.

SQIBS checks the Resolve filter before the Trigger filter, so a Trigger with no value opens an incident for every other message (any problem state) while recoveries resolve.

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 in Data Infrastructure Insights

  1. Go to Admin > Notifications and open the Webhooks tab. Click + Webhook.
  2. Give it a name, choose Template Type: Generic, and set URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=netappdii&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. Set Method to POST and keep the headers Content-Type: application/json and Accept: application/json.
  2. The generic template fills the message body in a Slack layout. Replace it with this flat JSON, which the filter above reads:
{
  "alertId": "%%alertId%%",
  "severity": "%%severity%%",
  "monitorName": "%%monitorName%%",
  "monitorType": "%%monitorType%%",
  "triggeredOn": "%%triggeredOn%%",
  "alertCondition": "%%alertCondition%%",
  "alertDescription": "%%alertDescription%%",
  "link": "https://%%cloudInsightsHostname%%%%alertRelativeUrl%%"
}
  1. Click Test Webhook, then Create Webhook.

Step 3: Send monitor alerts to the webhook

  1. Open a monitor (or create one) and, in Set up team notifications, choose Webhook as the delivery method.
  2. Select the alert levels Critical, Warning and Resolved, choose the SQIBS webhook, and save the monitor.

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. Click Test Webhook, or let a monitor alert.
  2. In SQIBS, a new incident opens, titled with the monitor name.
  3. When the alert is resolved, the same alertId arrives with the resolved level, 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 NetApp webhook.

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 Data Infrastructure Insights reports a volume over 90% full, SQIBS can run a workflow that grows the volume or clears old snapshots.

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: