> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring & Alerts via CloudWatch

> Monitor AutoMQ's Kafka-compatible metrics using CloudWatch for enhanced observability. Benefit from cloud-native scalability and cost efficiency.

Metrics are essential analytical data for system observability. AutoMQ supports exposing several native Apache Kafka® Metrics via CloudWatch.

## Metrics Collection and Application Principles

Internal components of AutoMQ support the collection of various Kafka Server Metrics data. However, the current business edition does not provide built-in Metrics dashboards and monitoring alert capabilities. Users can implement custom Metrics monitoring and analysis based on the integration features provided by AutoMQ. The overall architecture is referenced in the diagram below:

<img src="https://mintcdn.com/automq/6t03b99H9kP_jCZq/automq-cloud/monitoring-alert/monitoring-alert-via-cloudwatch/1.webp?fit=max&auto=format&n=6t03b99H9kP_jCZq&q=85&s=d12b5de04a25b97378f082e677074d57" width="2560" height="984" data-path="automq-cloud/monitoring-alert/monitoring-alert-via-cloudwatch/1.webp" />

Referencing the diagram above, use the Metrics integration feature [Manage Integrations▸](/automq-cloud/manage-environments/manage-integrations) to forward Metrics data to the CloudWatch service.

## CloudWatch Metrics Definition

Detailed definitions of the relevant Metrics exposed through the above integration are as follows:

| **Metric Name**<br />                     | **Metric Description**<br />                                                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| kafka\_controller\_active\_count<br />    | <ul><li>Meaning: The number of active Controller nodes, unit: count.</li><li>Dimension: Cluster</li></ul>                                   |
| kafka\_network\_io\_bytes\_in\_sec<br />  | <ul><li>Meaning: Write traffic throughput, unit: Byte/s.</li><li>Dimension: Cluster, Topic</li></ul>                                        |
| kafka\_network\_io\_bytes\_out\_sec<br /> | <ul><li>Meaning: Read traffic throughput, unit: Byte/s.</li><li>Dimension: Cluster, Topic</li></ul>                                         |
| kafka\_server\_connection\_count<br />    | <ul><li>Meaning: The number of client connections, unit: count.</li><li>Dimension: Cluster</li></ul>                                        |
| kafka\_partition\_total\_count<br />      | <ul><li>Meaning: The total number of partitions in the cluster, not considering replicas, unit: count.</li><li>Dimension: Cluster</li></ul> |
| kafka\_topic\_count<br />                 | <ul><li>Meaning: The total number of Topics in the cluster, unit: count.</li><li>Dimension: Cluster</li></ul>                               |
| kafka\_consume\_offset\_lag<br />         | <ul><li>Meaning: The number of messages accumulated for consumption, unit: count.</li><li>Dimension: Topic, Consumer Group</li></ul>        |
| kafka\_message\_count\_in\_sec<br />      | <ul><li>Meaning: The number of messages written per second, unit: messages/sec.</li><li>Dimension: Cluster, Topic</li></ul>                 |
| kafka\_partition\_offline\_count<br />    | <ul><li>Meaning: Number of offline, leaderless partitions in the cluster, measured in units.</li><li>Dimension: Cluster</li></ul>           |
| kafka\_log\_size<br />                    | <ul><li>Meaning: Size of message storage space, measured in Bytes.</li><li>Dimension: Cluster, Topic</li></ul>                              |