Receive accurate alerts based on performance anomalies in your application by activating alarms.
Start by adding recipients who will receive alarms. Alarms can be sent to email addresses, create push notifications to webhooks, sent to Slack, PagerDuty, Microsoft Teams, VictorOps, Signl4 and OpsGenie. You then need to assign recipients to specific alarms for them to receive the alerts. You can assign one or several recipients to an alarm. The status column will let you know if any issues reach the recipient.
Click Add new and choose what kind of alarm you want to configure. When configuring alarms, most of them involve setting a value threshold and a time threshold, for example, 1,000 connections for longer than 60 seconds. The time threshold will always be in seconds, but the value threshold can vary depending on the alarm. For example: percentage, gigabytes, or number.
Some alarms use filtering by regexp; for example, the regexp .* will match all queues. A regexp like ^myqueue$ would match exactly the queue named "myqueue". Leave these fields empty if you do not wish to apply any filtering. Use Rubular (a regular expression editor) to test your regex.
If an alarm has been triggered but not yet resolved, you can receive reminders that the alarm is still active. The minimum reminder interval is 30 seconds. Leave the reminder interval field empty or set it to “0” to not receive any reminders. Note that this doesn’t affect PagerDuty, VictorOps, or OpsGenie recipients since reminders are managed in those services. If an alarm has been ongoing for 30 days, it will be reset and might trigger again.
Alarm notifications can be received via webhooks. This describes the content payload that is being sent in each POST.
type | Type of alarm such as queue, consumer, cpu, memory, disk, connection, netsplit. |
appname | Name of the instance that triggered the alarm. |
hostname | Hostname of the instance that triggered the alarm. |
threshold | Value threshold specified for the alarm. |
vhost_regexp | regexp for the vhost. |
regexp | Regexp of your specified alarm (e.g., Queue regexp). |
time_until_fire | Time threshold specified for the alarm. |
options | Could include extra information about the alarm such as message_type (messages_unacknowledge, messages_ready, messages). |
account_id | Account id of the instance that triggered the alarm. |
Get notified on events such as planned and emergency maintenance and reboots.
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
This alarm is available on dedicated instances
If you enable this alarm, you will get notified when our monitor system cannot reach your server.
Some of the reasons why this could happen:
Time threshold |
[seconds]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
This alarm is available on dedicated instances
When CPU Alarm is enabled, you will receive a notification when the server is using more than, or equal to, the threshold of CPU usage as a percentage, for a given amount of time.
Time threshold |
[seconds]
|
Value threshold |
[number, 0-100]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
This alarm is available on dedicated instances
When Memory Alarm is enabled, you will receive a notification when the server is using more than, or equal to, the threshold of memory usage as a percentage for a given amount of time.
Time threshold |
[seconds]
|
Value threshold |
[number, 0-100]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
This alarm is available on dedicated instances
When Disk Alarm is enabled, you will receive a notification when there is less than, or equal to, the threshold of available disk left in GB, for a given amount of time.
Time threshold |
[seconds]
|
Value threshold |
[number]
|
Calculation |
[Fixed / Percentage]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
Consumers Alarms can be triggered to send notifications when the number of consumers for a queue is less than, or equal to, a given number of consumers for a given amount of time.
Value threshold |
[number of consumers]
|
Time threshold |
[seconds]
|
Queue regexp |
[regular expression]
|
VHost regexp |
[regular expression]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
Connection Alarms can be triggered to send notifications when the number of connections is greater than, or equal to, a given number of connections for a given amount of time in seconds.
Value threshold |
[number of connections]
|
Time threshold |
[seconds]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
Channel Alarms can be triggered to send notifications when the number of channels is greater than, or equal to, a given number of channels for a given amount of time in seconds.
Value threshold |
[number of channels]
|
Time threshold |
[seconds]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
The Connection Flow Alarm checks if a connection state has changed from running to flow. Connection Flow Alarms can be triggered to send notifications when a connection is in a flow state for a given amount of time.
Time threshold |
[seconds]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
Queue alarms can be triggered to send notifications when a number of messages in a queue reaches a certain threshold for a given amount of time.
Value threshold |
[number of messages in queue]
|
Time threshold |
[seconds]
|
Queue regexp |
[regular expression]
|
VHost regexp |
[regular expression]
|
Message type |
[Total, Total, Unacked, Ready, Ack, Ack rate, Deliver, Deliver rate, Deliver_get, Deliver_get rate, Deliver_no_ack, Deliver_no_ack rate, Get, Get rate, Get_empty, Get_empty rate, Get_no_ack, Get_no_ack rate, Publish, Publish rate, Redeliver, Redeliver rate] |
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |
This alarm is available on dedicated instances
This alarm will alert you when there is a netsplit between nodes, meaning that nodes cannot communicate with each other.
Time threshold |
[seconds]
|
Reminder interval |
[seconds]
This has no effect for PagerDuty, VictorOps, or OpsGenie recipients since reminders are built in to those serivces. |
Recipients |
[email address(es)]
Select where the alarm notifications should be sent, you can select multiple recipients separated by comma. |