CONFLUENT PLATFORM
Clicking the Alerts Triggers tab shows a summary of all configured triggers:
Initially, the Triggers page is blank when there aren’t any triggers defined yet.
Use the Triggers page to:
Use the New Trigger form to define the criteria that will activate associated alert actions. Some of the fields are already pre-populated when you clicked Set up an alert from a context menu.
The following component types of triggers can be created:
Use this broker trigger field reference for guidance when adding a broker trigger.
Broker trigger form
A unique name used to identify the trigger (for example: Broker fetch request latency).
Note
Uniqueness is not enforced. As a recommended best practice, use unique and descriptive names to avoid confusion.
Select a cluster to trigger based on conditions of individual brokers.
Warning
There is a known issue when multiple clusters are selected for a broker or cluster trigger. As a recommended best practice, only select a single cluster for the trigger. For more information, see the known issues section in the release notes.
Values in Metric are triggered on a per-broker basis.
Important
Any broker that meets the defined Condition will trigger individually.
Prior to Kafka 0.11.0.0, the BytesOutPerSec accounted for traffic from the consumer and internal replication. This has been changed to only account for consumer traffic for this broker. Adjust alerts accordingly.
BytesOutPerSec
Use this cluster trigger field reference for guidance when adding a cluster trigger.
Cluster trigger form
A unique name that identifies the trigger (for example: Control Center Cluster down).
Control Center Cluster down
Select a cluster to trigger based on a defined condition.
Values in Metric are triggered on a cluster-wide basis. A cluster that meets the defined Condition triggers an associated action.
Yes
Total number of topic partitions in the cluster that are offline. This can happen if the brokers with replicas are down, or if unclean leader election is disabled and the replicas are not in sync and thus none can be elected leader (may be desirable to ensure no messages are lost).
A trigger should be created for values > 0 (Greater than zero).
> 0
The number of unclean partition leader elections in the cluster reported in the last interval.
When unclean leader election is held among out-of-sync replicas, there is a possibility of data loss if any messages were not synced prior to the loss of the former leader. So if the number of unclean elections is greater than 0, investigate broker logs to determine why leaders were re-elected, and look for WARN or ERROR messages. Consider setting the broker configuration parameter unclean.leader.election.enable to false so that a replica outside of the set of in-sync replicas is never elected leader.
unclean.leader.election.enable
false
A trigger should be created for values != 0 (Not equal to zero).
!= 0
Total number of topic partitions in the cluster that are under-replicated; i.e., partition with number of in-sync replicas less than replication factor.
Use this consumer group trigger field reference for guidance when adding a consumer group trigger.
Consumer group alerts in Confluent Control Center are based on the total cumulative lag for all partitions in all topics consumed in a Consumer group.
Consumer group trigger form
A unique name used to identify the trigger (for example: consumer group name under consumption).
The metric to monitor:
Use this topic trigger field reference for guidance when adding a topic trigger.
Topic trigger form
A unique name used to identify the trigger (for example: topic name production requests).
A select list of options for matching against the value field (below). The name of the topic can Equals, Begins with, Ends with, or Contains a specified value.
For example, selecting Contains and then entering ‘topic’ into the value field will match ‘my topic’, ‘topical’, and ‘topics with data’. If Begins with is selected, the trigger will only match ‘topical’ and ‘topics with data’, not ‘my topic’.
The name or part of a topic name to be triggered against. Works in conjunction with Condition to match against one or more topics.
If multiple topics match against topic name, the trigger will be per topic, not an aggregate. In the case where there are two topics that Begin with ‘mytopic’; and the trigger is set to Bytes in for Metric, Greater than for Condition, and 100 for Value, any ‘mytopic’ matches will fire the trigger if they get > 100 Bytes In.
Bytes in
Greater than
100
A message appears when there are greater than five topics that match the criteria. Narrow the criteria if you see this message.
The value to check for the trigger alert. Possible values are:
Prior to Apache Kafka® 0.11.0.0, the BytesOutPerSec accounted for traffic from the consumer and internal replication. This has been changed to only account for consumer traffic for this topic. Adjust alerts accordingly.
Tip
See Example triggers for step-by-step trigger examples.