Overview
Send Kaseya VSA alarms to Callgoose SQIBS. Point a VSA notification that posts JSON (webhook) at your SQIBS API endpoint, and SQIBS opens an incident for each alarm, so the right engineer is paged and an automation workflow can start.
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 Kaseya VSA template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | (none) | Opens an incident for every alarm while you capture the payload. |
- Choose the Priority for these incidents and click Save.
Kaseya VSA 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 filter on the severity or alarm type field, set the title to the alarm name, and if VSA sends a closed or cleared message, add a resolve filter matched on the alarm ID.
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 the webhook in Kaseya VSA
- In VSA, open the notification (or integration) settings and add a webhook that is sent when an alarm is created.
- Set the URL to your SQIBS endpoint and the method to POST:
https://<your-endpoint>/sqibs-api/v1/process?from=kaseyavsa&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.
- Choose the organisations, policies or alarm types to send, save, and send a test.
If your VSA version has no webhook notifications, run a VSA agent procedure on alarm that calls curl (or Invoke-RestMethod on Windows) with a small JSON body to the same URL.
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.
- Trigger a test alarm, for example by lowering a disk space threshold on a test machine.
- In SQIBS, a new incident opens. Copy its keys into the filter with the JSON key creator.
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 VSA 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 VSA reports low disk space on a workstation, SQIBS can run a workflow that clears temporary files and rechecks the space.
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.