CloudAMQP offers various monitoring tools that will address performance issues promptly and automatically before they impact your business. CloudAMQP monitoring includes diagrams for CPU and Memory usage. It is possible to activate alarms that will be triggered when part of the system is heavily used. The RabbitMQ log stream is easy to view directly in CloudAMQP.
Receive accurate alerts based on performance anomalies in your application by activating Queue Alarms, Consumers Alarm, CPU Alarms, and Memory Alarms.
Alarms can be sent to email addresses, create push notifications to webhooks, sent to Slack, PagerDuty, Microsoft Teams, VictorOps, or OpsGenie. When an alarm is triggered, an alert is sent to everyone specified in the notifications list. You need to set up a notification before any of the alarms will work correctly. Learn more about payload sent when using a webook.
NOTE: The admin user must have access to all vhosts on the server for the queue and consumer alarms to work correctly.
Queue alarms can be activated for all instances.
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.
When a queue matches the given regexp and when that queue has had more than the value threshold (more than x messages in the queue) for more than a number of seconds , the alarm will trigger.
Example: The regexp
will match all your queues.
A regexp like
would match exactly the queue named "myqueue".
Use Rubular to test your regex.
Consumers alarms can be activated for all instances.
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.
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.
Connection Flow Alarms can be activated for all instances.
The Connection Flow Alarm checks if a connection state has been changed from running to flow. Connection Flow Alarms can be triggered to send notifications when a connection flow is in a flow state, for a given amount of time.
CPU Alarms are only available for dedicated instances.
When CPU Alarm is enabled you will receive a notification when you are using more than 80% of the available CPU for more than 15 minutes. This level can be modified. It is recommended to enable CPU Alarms, which can be done through the Control Panel.
Memory Alarms are only available for dedicated instances.
When Memory Alarms is enabled you will receive a notification when you are using more than 90% of the virtual machine's memory for more than 15-minutes. It is recommended to enable Memory Alarms, which can be done through the Control Panel.
Notice Alarms notifies you about CloudAMQP scheduled maintenance events such as planned and emergency maintenance and other critical information regarding your instance. You will be notified when your instance is scheduled for a reboot, including a time frame for when the reboot is planned. Notice Alarms are enabled through the Control Panel.
We recommend to set Notice Alarm and address important information about your cluster to where it makes sense. For your convenience, Notice Alarms cannot be removed or unsubscribed from.
Server Metrics measure performance metrics from your server. CloudAMQP shows CPU Usage Monitoring and Memory Usage Monitoring.
CPU Usage refers to how much work your processor is doing.
I/O Wait: Shows the percentage of time spent by the CPU waiting for an IO (input/output) operation to complete, in other words, the percentage of time the CPU has to wait on the disk. If this is high you should consider if more messages can be published as transient instead of persistent or make sure that your queues are short so that messages don't have to be written to disk. You can also contact our support to discuss other solutions.
User time: Shows the percentage of time your program spends executing instructions in the CPU. In this case, the time the CPU spent running RabbitMQ.
If this is high it probably means you are near the limit of what your server can handle. You should consider upgrading before the lack of CPU power becomes a serious issue.
System time: Describes the percentage of time the CPU spent running OS tasks.
Steal time: The percentage of CPU time "stolen" by the virtualization system, or time spent when the virtual CPU waits for a real CPU. If this is high it may mean that you are using to much CPU power, which can seriously impact the performance of your server. You should probably upgrade to a larger instance.
RabbitMQ Log Stream shows a live log from RabbitMQ.
Integrated monitoring services are only available for dedicated instances.
CloudAMQP has integrated log and metric services including CloudWatch, Papertrail, Logentries, Stackdriver, Loggly, Splunk, DataDog, Librato, and New Relic. Learn more about our available CloudAMQP monitoring services.
Alarm notifications can be received via webhooks. This section describes the content payload that is being sent in each POST.