Overview
Send AimBetter database and server monitoring alerts to Callgoose SQIBS. AimBetter posts each alert to your SQIBS API endpoint. SQIBS opens an incident when an alert fires and resolves it when AimBetter sends the resolved notification.
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 AimBetter template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "status" |
firing |
Opens an incident. |
| Resolve | "status" |
resolved |
Resolves the open incident. |
| Match | "alert_id" |
Ties the resolve message 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.
AimBetter's exact field names were not confirmed for this page. Use the values above as a starting point and adjust them from your first test message.
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 in AimBetter
- In AimBetter, open the notification settings and add a webhook destination.
- Enter your SQIBS endpoint as the URL, with method POST and content type
application/json:
https://<your-endpoint>/sqibs-api/v1/process?from=aimbetter&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.
- Turn on resolved (clear) notifications so SQIBS can resolve incidents, then save and send a test.
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.
- Send a test from the webhook settings, or let a test alert fire.
- In SQIBS, a new incident opens. 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.
{
"status": "firing",
"alert_id": "aim-000123",
"alert_name": "High DB CPU",
"severity": "critical",
"description": "CPU on db-prod-1 above 90% for 3 minutes",
"labels": {
"host": "db-prod-1"
}
}
- When the alert clears, the resolved notification closes 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 AimBetter webhook.
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 AimBetter reports a blocking query on a database, SQIBS can run a workflow that collects the session details and kills the blocker if it matches a known pattern.
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.