Overview
Send Auvik network alerts to Callgoose SQIBS. A webhook integration posts each alert to your SQIBS API endpoint. SQIBS opens an incident when an alert triggers and resolves it when Auvik clears it.
How it works
Triggered opens it, Cleared 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
- In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
- In Select Integration Template, choose Auvik. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "alertStatusString" |
triggered |
Opens an incident. |
| Resolve | "alertStatusString" |
cleared |
Resolves the open incident. |
| Match | "entityId" |
Ties the resolve message to the incident it opened. | |
| Title from | "subject" |
Becomes the incident title. | |
| Description from | "alertDescription" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
The template matches the resolve message on "entityId", which Auvik often sends empty. Change Map incident with (trigger and resolve) to "alertId", which is the same in the triggered and cleared messages.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 integration in Auvik
- In Auvik, go to Integrations and click Add Integration, then choose Webhook.
- Give it a name, for example
CallgooseSQIBS, and in Webhook URL enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=auvik&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.
- Click Test Connection, then Save.
Step 3: Send alerts to the webhook
- Go to Manage Alerts > Notification Channels and add a channel with Contact Method set to Webhook (the integration from step 2).
- In Manage Alerts, add or edit an alert, choose its severity and rule, and select the webhook channel under Notification.
- Save the alert.
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.
- Click Test Connection in the integration, or let an alert trigger.
- In SQIBS, a new incident opens. Auvik's payload looks like this (shortened):
{
"subject": "You have a new alert!",
"alertStatusString": "Triggered",
"alertId": "MTE1OTc0Nzc4Mzc5NDg5NzY2MSwxMTU5NzQ3Nzc4MzUyNzg3ODA4",
"alertName": "Device offline",
"entityName": "core-switch-01",
"companyName": "Head office",
"alertDescription": "core-switch-01 is not responding",
"alertSeverityString": "Critical",
"date": "2026-11-22T10:53:24.033Z",
"entityId": null
}
- When the alert clears, Auvik sends
"alertStatusString": "Cleared"with the samealertId, 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 Auvik integration.
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 Auvik reports a switch port flapping, SQIBS can run a workflow that collects the interface counters and bounces the port.
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:
- Select Workflow: choose the automation workflow to run when this filter opens an incident.
- If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
- 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:
- Prometheus: incident auto remediation, a full worked example.
- Automation workflow: build a workflow from actions.
- Run workflows where your systems are: SSH, Bash, PowerShell, Python, Ansible, kubectl, Terraform.