All Products
Search
Document Center

ApsaraMQ for Kafka:Configure alerts in Control Center

Last Updated:Mar 11, 2026

ApsaraMQ for Confluent clusters generate metrics across brokers, topics, and consumer groups. Control Center evaluates these metrics against thresholds you define, and sends notifications through email, Slack, or PagerDuty when anomalies occur -- helping you detect broker failures, consumer lag spikes, or cluster outages before they affect production workloads.

How it works

An alert consists of two parts:

  • Trigger: A rule that evaluates a metric against a threshold. When the condition is met, the trigger fires.

  • Action: A notification sent when a trigger fires. Each trigger can have one or more actions.

To set up an alert:

  1. Create a trigger by selecting a metric, a condition (such as "greater than"), and a threshold value.

  2. Create an action that specifies the notification channel (email, Slack, or PagerDuty) and link it to a trigger.

When the metric meets the trigger condition, all associated actions run and send notifications.

Create a trigger

  1. Log on to Control Center.

  2. In the top navigation bar, click the image.png icon.

  3. On the Overview page, click the Triggers tab, and then click Add a trigger.

  4. On the New trigger page, specify the trigger name and trigger condition, and then click Save.

After you create the trigger, click the trigger name on the Triggers tab to modify or delete it.

Create an action

Actions define how notifications are delivered when a trigger fires.

  1. On the Overview page, click the Actions tab, and then click Add an action.

  2. On the New action page, configure the following parameters, and then click Save.

    ParameterDescription
    Action NameA name for the action.
    TriggersThe trigger to associate with this action.
    ActionThe notification channel. Valid values:
    - Send email: Deliver notifications by email.
    - Send PagerDuty notification: Deliver notifications through PagerDuty. For setup details, see Services and Integrations.
    - Send Slack notification: Deliver notifications through Slack incoming webhooks. For setup details, see Sending messages using incoming webhooks.


    SubjectEmail addresses of one or more alert contacts, separated by commas. Required only when Action is set to Send email. Each time the action runs, an email is sent to the specified addresses.
    Max send rateMaximum number of times the action runs within a given frequency. Use with the Frequency parameter. For example, set this to 1 and Frequency to Per day to limit notifications to once per day.
    FrequencyThe time interval for the send rate limit. Valid values: Per minute, Per hour, Per 4 hours, Per 8 hours, Per day. Default: Per hour.

After you create the action, click the action name on the Actions tab to modify or delete it.

Pause and resume all alert actions

During maintenance or troubleshooting, pause all alert actions to suppress notifications temporarily. Pausing does not change individual action settings. Each action retains its enabled or disabled state.

While paused, trigger conditions that are met are ignored and all enabled actions associated with those triggers are suppressed.

After you resume actions, triggers fire and send notifications when conditions are met again.

If you stop and restart ApsaraMQ for Confluent or Control Center, paused actions automatically resume and become active.

Pause all actions

  1. On the Overview page, click the Actions tab.

  2. Turn on the Pause all actions switch.

  3. Read the confirmation message and click Confirm.

Resume all actions

  1. On the Overview page, click the Actions tab.

  2. Turn off the Pause all actions switch.

  3. Read the confirmation message and click Confirm.

Disable or enable an alert action

Actions are enabled by default when created. Disable an action to prevent it from running without deleting it. Pausing and resuming respects the disabled state -- resuming paused alerts does not reactivate disabled actions.

  1. On the Overview page, click the Actions tab.

  2. Click the action to manage.

  3. On the action details page, click Edit and turn off the Enabled switch.

To re-enable the action, repeat these steps and turn on the Enable switch.

Alert metrics reference

Control Center provides four categories of trigger metrics. Each metric monitors a specific aspect of your Kafka infrastructure.

Broker metrics

Broker triggers monitor individual broker performance.

MetricDescription
Bytes inBytes produced per second.
Bytes outBytes fetched per second. Internal replication traffic is excluded.
Fetch request latencyLatency of fetch requests at the median, 95th, 99th, or 99.9th percentile. Unit: milliseconds.
Production request countTotal production requests per minute.
Production request latencyLatency of production requests at the median, 95th, 99th, or 99.9th percentile. Unit: milliseconds.

Cluster metrics

Cluster triggers monitor overall cluster health and availability.

MetricDescriptionRecommended threshold
Cluster downWhether a monitored cluster is shut down.--
Leader election rateNumber of partition leader elections.--
Offline topic partitionsTotal topic partitions that are offline in the cluster. Partitions go offline when brokers with replicas are down, or when unclean leader election is disabled and no in-sync replica can be elected leader. In the latter case, ensure that no messages are lost.Greater than 0
Unclean election countNumber of unclean partition leader elections reported in the last interval. Data loss may occur if messages were not synced before the former leader was lost. If the number of unclean elections is greater than 0, query the broker logs to determine why leaders were re-elected and search for warning or error messages. We recommend that you set the broker configuration parameter unclean.leader.election.enable to false to prevent out-of-sync replicas from being elected leader.Not equal to 0
Under replicated topic partitionsTotal topic partitions where the number of in-sync replicas is less than the replication factor.Greater than 0
ZK DisconnectedWhether brokers can connect to ZooKeeper. Valid values: Offline, Online.--
ZooKeeper expiration rateRate at which ZooKeeper session expirations occur across brokers.--

Consumer group metrics

Consumer group triggers detect consumption delays and performance degradation.

MetricDescription
Average latencyAverage latency of a consumer group. Requires a Confluent Monitoring Interceptor configured for clients in the consumer group. Unit: milliseconds.
Consumer lagHow far behind consumer applications are from producers. Calculated as the difference between the end offset and the current offset.
Consumer leadHow far ahead consumer applications are from the earliest available messages. Calculated as the difference between the current offset and the beginning offset. For example, a consumer at offset 15 in a partition that starts at offset 0 has a lead of 15. A shrinking lead indicates that consumption is approaching the earliest available data, which can be used to determine whether data loss occurred.
Consumption differenceDifference between the expected consumption value and the actual consumption value within a specific time period. A small gap close to real time is normal and diminishes over time.
Maximum latencyMaximum latency of a consumer group. Requires a Confluent Monitoring Interceptor configured for clients in the consumer group. Unit: milliseconds.

Topic metrics

Topic triggers monitor data flow and replication health for specific topics.

MetricDescription
Bytes inBytes coming into a topic per second.
Bytes outBytes going out of a topic per second. Internal replication traffic is excluded.
Out of sync replica countTotal topic partition replicas that are in sync with the leader in the cluster. This value is the product of topic partitions multiplied by the topic replication factor.
Production request countNumber of production requests to a topic in the cluster.
Under replicated topic partitionsNumber of under-replicated topic partitions. Use this metric to determine whether a Kafka broker crash is caused by a specific topic partition.

Trigger conditions

A trigger fires when the detected metric value meets the configured condition against the threshold.

ConditionFires when
Equal toThe metric value equals the threshold.
Greater thanThe metric value exceeds the threshold.
Less thanThe metric value is below the threshold.
Not equal toThe metric value differs from the threshold.

Related information

For more information about Control Center alert capabilities, see Control Center Alerts for Confluent Platform.