Overview
Send WebSitePulse alerts to Callgoose SQIBS. A URL contact 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 WebSitePulse template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | (none) | No key yet: every alert opens an incident. |
- Choose the Priority for these incidents and click Save.
Send one test alert, then refine the filter with the JSON key creator: add a key for failure alerts, a Resolve filter for recovery messages, and a Match key for the target. If the API log shows the alert as form data instead of JSON, the filter cannot read its fields; keep this catch-all filter.
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 URL contact in WebSitePulse
- In WebSitePulse, open Targets and create the target to monitor (Create New Target), if needed.
- Go to Contacts and, under URL Contact, click Create New. Set a Label and the URL to your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=websitepulse&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 POST, set the active period, and add a rule that links the target and the alert types (for example connection problems and recovery messages) to this contact.
- Review and Save.
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.
- Point a test target at an address that does not answer.
- In SQIBS, a new incident opens. Open the payload in the JSON key creator and refine the filter.
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 URL contact.
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 WebSitePulse reports a site down, SQIBS can run a workflow that restarts the web service and rechecks.
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.