Overview

Send CloudAMQP alarms to Callgoose SQIBS. A webhook recipient posts each alarm, such as high CPU, memory or queue length, to your SQIBS API endpoint. SQIBS opens an incident when the alarm fires and resolves it when CloudAMQP reports it resolved.

You need
A CloudAMQP instance with admin access, and a SQIBS API token
Setup time
About 10 minutes
Result
CloudAMQP alarms open and resolve SQIBS incidents

How it works

CloudAMQP
Alert fires
An alarm threshold is crossed on the instance.
CloudAMQP
Sends a webhook
To a webhook recipient, as JSON.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
resolved: false opens it, true 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

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. In Select Integration Template, choose CloudAMQP. It fills in these filter values:
Part Payload JSON key Key value contains What it does
Trigger "resolved" false Opens an incident.
Resolve "resolved" true Resolves the open incident.
Match "account_id" Ties the resolve message to the incident it opened.
Title from "subject" Becomes the incident title.
  1. Choose the Priority for these incidents and click Save.

The template matches on "account_id", so all alarms of the account share one incident. If you run several alarms, change Map incident with (trigger and resolve) to "type" so each alarm type has its own incident.

The template is a starting point, not a lock-in: every value stays visible and you can change it.

Find the right key with the JSON key creator
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 recipient in CloudAMQP

  1. In the CloudAMQP console, open the instance and go to the Alarms tab.
  2. Click Add new recipient, choose Webhook, and give it a name, for example Callgoose SQIBS.
  3. In Webhook URL, enter your SQIBS endpoint:
https://<your-endpoint>/sqibs-api/v1/process?from=cloudamqp&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.

  1. Click Create recipient, then add the recipient to the alarms you want (CPU, memory, disk, queue).

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.

  1. Click Trigger on the recipient to send a test alarm.
  2. In SQIBS, a new incident opens, titled with the alarm subject. CloudAMQP's payload looks like this (shortened):
{
  "appname": "orders-broker",
  "account_id": "48717df2-7b13-4477-aa42-d4d8f459dba0",
  "type": "queue",
  "hostname": "possum.lmq.cloudamqp.com",
  "resolved": false,
  "subject": "Queue orders has more than 10000 messages",
  "threshold": 10000
}
  1. When the alarm clears, CloudAMQP sends "resolved": true and SQIBS 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 CloudAMQP recipient.

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 CloudAMQP reports a queue backing up, SQIBS can run a workflow that scales out the consumer service.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

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:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. 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: