Overview
Send Tencent Cloud alarms to Callgoose SQIBS. A notification template in Tencent Cloud Observability Platform (Cloud Monitor) calls your SQIBS API endpoint when an alarm is triggered and when it recovers. SQIBS opens an incident on the alarm and resolves it on the recovery.
How it works
alarmStatus 1 opens it, 0 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 Tencent Cloud template yet, so enter them by hand):
| Part | Payload JSON key | Key value contains | What it does |
|---|---|---|---|
| Trigger | "alarmStatus" |
1 |
Opens an incident. |
| Resolve | "alarmStatus" |
0 |
Resolves the open incident. |
| Match | "alarmPolicyInfo"."policyId" |
Ties the resolve message to the incident it opened. | |
| Title from | "alarmPolicyInfo"."policyName" |
Becomes the incident title. | |
| Description from | "alarmObjInfo" |
Becomes the incident description. |
- Choose the Priority for these incidents and click Save.
policyId is the alarm policy, so all instances under one policy share an incident. These values follow the payload shown in the test step. Send one test notification first and confirm the keys with the JSON key creator: Tencent Cloud can change its payload between versions, and SQIBS matches key names exactly (upper and lower case matter).
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 an API callback to a notification template
- In the Tencent Cloud console, open Tencent Cloud Observability Platform > Alarm Management > Notification Template and create a template.
- Under the API callback, enter your SQIBS endpoint and choose to be notified for both alarm triggering and alarm recovery:
https://<your-endpoint>/sqibs-api/v1/process?from=tencentcloud&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.
- Save, then go to Policy Management, open each alarm policy that should page through SQIBS, and bind the template.
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.
- Trigger a test alarm, for example by lowering a threshold on an instance.
- In SQIBS, a new incident opens, titled with the policy name. A callback looks like this (shortened):
{
"sessionId": "xxxxxxxx",
"alarmStatus": "1",
"alarmType": "metric",
"alarmObjInfo": {
"region": "ap-singapore",
"namespace": "qce/cvm",
"dimensions": {
"unInstanceId": "ins-o9p3rg3m"
}
},
"alarmPolicyInfo": {
"policyId": "policy-n4exeh88",
"policyName": "Disk usage above 90%",
"policyType": "cvm_device"
},
"firstOccurTime": "2026-11-22 10:00:00"
}
- Put the threshold back. The recovery callback with
"alarmStatus": "0"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 notification template.
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 a Tencent Cloud alarm reports a disk above 90% on a CVM instance, SQIBS can run a workflow that clears old logs and rechecks the space.
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.