This alert monitors the CPU utilization of Amazon MQ brokers. Sustained high CPU usage can affect broker performance and responsiveness. The alert is triggered when CPU utilization exceeds 90% within a 10-minute period. Monitoring this metric ensures the broker can handle workloads efficiently. Customization Guidance: - Threshold: Adjust the CPU utilization threshold based on your workload requirements and broker capacity. - Monitoring Period: Modify the monitoring period to match the response times of your application. - Notification Frequency: Set notification frequency to ensure timely intervention without flooding your alerting system. Action: If triggered, scale broker resources or optimize message processing to reduce CPU load.

This alert monitors the number of unacknowledged messages on Amazon MQ brokers. A high count may indicate message processing delays or application issues. The alert is triggered when the number of unacknowledged messages exceeds 1,000 within a 10-minute period. Monitoring this metric helps detect message processing bottlenecks. Customization Guidance: - Threshold: Adjust the unacknowledged message threshold based on application throughput and tolerance for delays. - Monitoring Period: Tailor the monitoring period to your application's message acknowledgment requirements. - Notification Frequency: Configure frequency to avoid alert fatigue while ensuring timely intervention. Action: If triggered, investigate application message acknowledgment behavior or broker resource utilization to resolve delays.

This alert monitors the memory utilization of Amazon MQ brokers. High memory utilization can lead to degraded broker performance, delayed message processing, or system instability. The alert is triggered when memory utilization exceeds 85% within a 10-minute period. Monitoring this metric ensures the broker has sufficient memory resources for smooth operations. Customization Guidance: - Threshold: Set the memory utilization threshold based on the memory requirements of your applications and workloads. - Monitoring Period: Adjust the monitoring period to reflect typical memory consumption patterns. - Notification Frequency: Modify notification frequency to balance prompt intervention and alert overload. Action: If triggered, investigate broker resource usage, optimize message processing, or scale the broker to handle higher workloads.

This alert monitors the number of consumers on Amazon MQ brokers. A sudden increase in consumer count could indicate issues with message consumption, possibly affecting system performance. The alert is triggered when the consumer count exceeds 1000 consumers within a 5-minute period. Action: Investigate unusual increases in consumer activity or check for message backlog issues. Customization Guidance: - Threshold: Adjust the consumer count threshold based on the expected number of consumers and traffic load. - Monitoring Period: Tailor the period to match the frequency of consumer activity in your environment. - Notification Frequency: Configure notification frequency to avoid unnecessary alerts while maintaining effectiveness. Action: If this alert is triggered, investigate consumer activity or check for message backlog issues.