Overview
Send SCOM alerts to Callgoose SQIBS. SCOM has no built-in webhook, so a command notification channel runs a short PowerShell script that posts each alert to your SQIBS API endpoint. SQIBS opens an incident for a new alert and resolves it when the alert is closed in SCOM.
How it works
new opens it, closed 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.
- Add a filter with these values (there is no built-in Microsoft SCOM template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "state" |
new |
Opens an incident. |
| Resolve | "state" |
closed |
Resolves the open incident. |
| Match | "alert_id" |
Ties the closed alert to the incident it opened. | |
| Title from | "alert_name" |
Becomes the incident title. | |
| Description from | "description" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
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 PowerShell script
Save this script on every management server in the notifications resource pool, for example as C:\Scripts\Send-ToCallgoose.ps1:
# C:\Scripts\Send-ToCallgoose.ps1 - called by the SCOM command notification channel.
param([string]$AlertId, [string]$AlertName, [string]$Severity, [string]$ResolutionState,
[string]$Source, [string]$Description)
$uri = "https://<your-endpoint>/sqibs-api/v1/process?from=scom&token=<your-token>"
$state = if ($ResolutionState -eq "255") { "closed" } else { "new" }
$body = @{ alert_id = $AlertId; alert_name = $AlertName; severity = $Severity; state = $state;
source = $Source; description = $Description } | ConvertTo-Json
Invoke-RestMethod -Method Post -Uri $uri -ContentType "application/json" -Body $body
Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.
Step 3: Create the command channel
- In the Operations console, go to Administration > Notifications > Channels, click New > Command.
- Name it
Callgoose SQIBS. Set Full path of the command file toC:\Windows\System32\WindowsPowerShell\v1.0\powershell.exeand Startup folder toC:\Scripts. - Set Command line parameters to:
-ExecutionPolicy Bypass -File "C:\Scripts\Send-ToCallgoose.ps1" -AlertId "$Data[Default='']/Context/DataItem/AlertId$" -AlertName "$Data[Default='']/Context/DataItem/AlertName$" -Severity "$Data[Default='']/Context/DataItem/Severity$" -ResolutionState "$Data[Default='']/Context/DataItem/ResolutionState$" -Source "$Data[Default='']/Context/DataItem/ManagedEntityPath$\$Data[Default='']/Context/DataItem/ManagedEntityDisplayName$" -Description "$Data[Default='']/Context/DataItem/AlertDescription$"
- Click Finish.
Step 4: Subscribe the channel to alerts
- Go to Notifications > Subscribers, add a subscriber named
Callgoose SQIBS, and give it an address that uses theCallgoose SQIBScommand channel. - Go to Notifications > Subscriptions and create a subscription with the criteria you want (for example severity Critical) and with a resolution state of New (0) or Closed (255), so both the new alert and its closure are sent.
- Add the
Callgoose SQIBSsubscriber and the command channel, and finish.
Step 5: 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.
- Raise a test alert, for example by stopping a monitored Windows service on a test server.
- In SQIBS, a new incident opens, titled with the alert name.
- Close the alert in SCOM (or let the monitor recover). The subscription runs the script with resolution state 255, 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 script (run it by hand with test values).
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 SCOM reports a stopped Windows service, SQIBS can run a PowerShell workflow that starts it again and checks it stays up.
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.