Skip to main content
AutoMQ integrates with Prometheus, enabling the transfer of Metrics data to Prometheus. This allows users to configure custom alert rules using Prometheus for the monitoring of unusual conditions like business pressure levels.

​
Alert Templates

The AutoMQ team has crafted a series of alert templates based on Metrics commonly utilized in production environments. These templates allow users to choose and set up alert rules according to their specific requirements.
To get the Prometheus alert rule templates mentioned below, you can reach out to the AutoMQ team by filling out this form.
The list of alert rule templates is as follows:
Alert Rule Item
Function and Scenario
HighTopicBytesInPerSec
  • Alert Rule: High alert for topic data write throughput
  • Function and Scenario: Monitor if the data write volume per second for a specified topic exceeds the threshold. Typically used for monitoring sudden bursts in write traffic.
HighTopicBytesInPerSecDayToDayChange
  • Alert Rule: High alert for day-to-day increase in topic data write throughput
  • Function and Scenario: Monitor if the day-to-day increase rate in data write volume per second for a specified topic exceeds the threshold. Generally used for monitoring sudden bursts in write traffic.
LowTopicBytesInPerSec
  • Alert Rule: Low alert for topic data write throughput
  • Function and Scenario: Monitor if the data write volume per second for a specified topic falls below the threshold. Typically used to detect write link damage or drop to zero.
LowTopicBytesInPerSecDayToDayChange
  • Alert Rule: Alert for day-to-day decrease in topic data write throughput
  • Function and Scenario: Monitor if the day-to-day decrease rate in data write volume per second for a specified topic exceeds the threshold. Usually employed to monitor write link damage or business fluctuations.
HighTopicBytesOutPerSec
  • Alarm Rule: High topic data read throughput alert
  • Purpose and Scenario: Monitor if the data read per second on a specified topic exceeds the threshold, typically used for monitoring burst reads and fanout traffic.
HighTopicBytesOutPerSecDayToDayChange
  • Alarm Rule: High day-to-day growth in topic data read throughput alert
  • Purpose and Scenario: Monitor if the day-to-day growth rate of data read per second on a specified topic exceeds the threshold, generally used for monitoring burst read traffic.
LowTopicBytesOutPerSec
  • Alarm Rule: Low topic data read throughput alert
  • Purpose and Scenario: Monitor if the data read per second on a specified topic falls below the threshold, typically used for monitoring potential link degradation or drops to zero.
LowTopicBytesOutPerSecDayToDayChange
  • Alarm Rule: Day-to-day drop in topic data read throughput exceeding threshold alert
  • Purpose and Scenario: Monitor if the day-to-day drop rate of data read per second on a specified topic exceeds the threshold, generally used for monitoring data flow degradation or business fluctuations.
HighGroupConsumeRatePerTopic
  • Alarm Rule: Consumer group high consumption rate alert
  • Purpose and Scenario: Monitor if the consumption rate per second in a specified consumer group exceeds the threshold, generally used for monitoring potential read anomalies.
LowGroupConsumeRatePerTopic
  • Alert Rule: Consumer Group Low Consumption Rate Alert
  • Function and Scenario: Monitors the specified Consumer Group to check if the number of messages consumed per second falls below a threshold, typically used to detect reading anomalies.
HighGroupConsumerLag
  • Alert Rule: Consumer Group Consumption Lag Alert
  • Function and Scenario: Monitors the specified Consumer Group to determine if the consumption lag exceeds a threshold, usually applied to detect reading anomalies.