Overview
Send HyperDX alerts to Callgoose SQIBS. HyperDX is now part of ClickHouse ClickStack; the alerting works the same way. You add SQIBS as a generic webhook, then choose it as the destination of a saved search or chart alert. SQIBS opens an incident each time the alert fires.
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.
- In Select Integration Template, choose HyperDX. It fills in these filter values:
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "title" |
Alert |
Opens an incident. |
| Title from | "title" |
Becomes the incident title. |
- Choose the Priority for these incidents and click Save.
HyperDX sends nothing when an alert clears, so close these incidents in SQIBS once the issue is fixed.
The template is a starting point, not a lock-in: every value stays visible and you can change it.
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 SQIBS as a generic webhook
- In HyperDX, open Team Settings and find the webhooks section. Add a Generic webhook.
- Give it a name, for example
CallgooseSQIBS, and in Webhook URL enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=hyperdx&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.
- In the custom body, paste:
{
"title": "{{title}}",
"body": "{{body}}",
"link": "{{link}}"
}
- Save the webhook.
Step 3: Send an alert to SQIBS
Open a saved search or a chart, click Alert, set the condition, choose Webhook and pick CallgooseSQIBS. Save the alert.
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.
- Set an alert threshold that the current data already breaks.
- In SQIBS, a new incident opens, titled with the alert title, with the matching lines in the description.
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 HyperDX 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 HyperDX finds a burst of database connection errors in the logs, SQIBS can run a workflow that restarts the connection pool.
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.