Overview
Send Cisco Catalyst Center (formerly DNA Center) events to Callgoose SQIBS. Catalyst Center posts the events you subscribe to, such as Assurance issues for devices and the network, to a webhook destination that points at your SQIBS API endpoint. SQIBS opens an incident for each.
How it works
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.
- Add a filter with these values (there is no built-in Catalyst Center template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "severity" |
Opens an incident for every event sent. Limit the events in the subscription. | |
| Title from | "name" |
Becomes the incident title. | |
| Description from | "description" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
Assurance issue updates carry a status such as active or resolved under "details". To resolve incidents automatically, add a Resolve filter on that status, matched on "instanceId", after checking a real resolved event in the API log.
Not sure of a key? Send one test message first (step below), then build the filter from the real payload.
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 destination
- In Catalyst Center, open System > Settings > External Services > Destinations, choose Webhook, and add a destination named
Callgoose SQIBS. - Enter your SQIBS endpoint as the URL, method POST, no authentication:
https://<your-endpoint>/sqibs-api/v1/process?from=catalystcenter&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.
- Save the destination.
Step 3: Subscribe to events
- Open Platform > Developer Toolkit > Event Notifications and create a subscription.
- Choose the events (for example Assurance issues with severity P1 and P2) and the
Callgoose SQIBSwebhook destination. - Save and use Try it to send a sample event.
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.
- Send a sample event from the subscription.
- In SQIBS, a new incident opens, titled with the event name. The payload below shows the shape to expect. Field names can differ between versions, so send one test message first and copy the exact keys from the API log with the JSON key creator.
{
"eventId": "NETWORK-DEVICES-3-251",
"namespace": "ASSURANCE",
"name": "Interface down",
"description": "Interface GigabitEthernet1/0/24 on edge-sw-07 is down",
"type": "NETWORK",
"category": "ALERT",
"severity": 2,
"timestamp": 1763806500000,
"details": {
"Device": "10.10.20.7",
"Assurance Issue Status": "active"
},
"instanceId": "1f6b2b4c-8d3a-4a8f-9c1e-2b7c5d9e0a11"
}
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 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 Catalyst Center reports an access switch interface down, SQIBS can run a workflow that bounces the port and checks the connected device.
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.