Overview
SolarWinds has retired AppOptics: it is no longer accessible, and its users move to SolarWinds Observability SaaS. Send your alerts to Callgoose SQIBS from there: a webhook notification service posts each alert to your SQIBS API endpoint, and SQIBS opens an incident for it.
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 SolarWinds Observability template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "triggerId" |
Opens an incident for every alert. | |
| Match | "triggerId" |
Identifies the alert event. | |
| Title from | "name" |
Becomes the incident title. | |
| Description from | "condition" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
To page only on critical alerts, set Key value contains to Critical on "severity" instead.
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 notification service
- In SolarWinds Observability SaaS, go to Settings > Notification Services > Webhook and click Create Configuration.
- Name it
Callgoose SQIBSand choose the POST method. - In the URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=solarwinds-observability&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.
- Keep the content type as JSON, and put this in HTTP POST Body (the triple braces keep the link unescaped):
{
"name": "{{name}}",
"severity": "{{severity}}",
"priority": "{{priority}}",
"condition": "{{condition}}",
"triggerId": "{{triggerId}}",
"detailUrl": "{{{detailUrl}}}",
"description": "{{description}}"
}
- Click Notification Test, then Create.
Step 3: Use it in alert definitions
In each alert definition, add the Callgoose SQIBS webhook as a notification and save it.
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 Notification Test in the webhook configuration, or let an alert fire.
- In SQIBS, a new incident opens, titled with the alert name.
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 configuration.
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 SolarWinds Observability reports an application's error rate rising, SQIBS can run a workflow that restarts the application pods.
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.