The minimum Network processor average idle percent for trigger expression.

-

The minimum Request handler average idle percent for trigger expression.

Filter of discoverable topics

Filter to exclude discovered topics

-

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

Number of leader elections per second.

Number of “unclean” elections per second.

Preprocessing:

- CHANGE_PER_SECOND

One indicates that the broker is the controller for the cluster.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The number of ineligible pending replica deletes.

The number of pending replica deletes.

The number of ineligible pending topic deletes.

The number of pending topic deletes.

The number of offline log directories (for example, after a hardware failure).

Number of partitions that don't have an active leader.

The rate at which data is fetched and read from the broker by consumers.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which bytes rejected per second by the broker.

Preprocessing:

- CHANGE_PER_SECOND

Number of client fetch request failures per second.

Preprocessing:

- CHANGE_PER_SECOND

Number of failed produce requests per second.

Preprocessing:

- CHANGE_PER_SECOND

Indicates the percentage of time that the request handler (IO) threads are not in use.

Preprocessing:

- MULTIPLIER: 100

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time in ms to serve the Fetch-Consumer request.

Time in ms to serve the Fetch-Consumer request for 95th percentile.

Time in ms to serve the specified Fetch-Consumer for 99th percentile.

Average time in ms to serve the Fetch-Follower request.

Time in ms to serve the Fetch-Follower request for 95th percentile.

Time in ms to serve the Fetch-Follower request for 99th percentile.

Average time in ms to serve the Produce request.

Time in ms to serve the Produce requests for 95th percentile.

Time in ms to serve the Produce requests for 99th percentile.

Average time for a request to update metadata.

Time for update metadata requests for 95th percentile.

Time for update metadata requests for 99th percentile.

The maximum of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The maximum of temporary memory used for converting message formats and decompressing messages.

The amount of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The average percentage of time that the network processors are idle.

Preprocessing:

- MULTIPLIER: 100

Number of requests waiting in producer purgatory.

Number of requests waiting in fetch purgatory.

The maximum lag between the time that messages are received by the leader replica and by the follower replicas.

The number of partitions under the minimum In-Sync Replica (ISR) count.

The number of partitions that have not been fully replicated in the follower replicas (the number of non-reassigning replicas - the number of ISR > 0).

The rate at which the number of ISRs in the broker increases.

Preprocessing:

- CHANGE_PER_SECOND

Rate of replicas leaving the ISR pool.

Preprocessing:

- CHANGE_PER_SECOND

The number of replicas for which this broker is the leader.

The number of partitions in the broker.

The number of reassigning leader partitions on a broker.

The size of the delay queue.

Current version of broker.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Service uptime in seconds.

Preprocessing:

- JAVASCRIPT: return (Math.floor((Date.now()-Number(value))/1000))

Latency in milliseconds for ZooKeeper requests from broker.

Connection status of broker's ZooKeeper session.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

ZooKeeper client disconnect per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client session expiration per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client readonly per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client sync per second.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data is fetched and read from the broker by consumers (by topic).

Preprocessing:

- CHANGE_PER_SECOND

Rejected bytes rate by topic.

Preprocessing:

- CHANGE_PER_SECOND

Unclean leader elections occur when there is no qualified partition leader among Kafka brokers. If Kafka is configured to allow an unclean leader election, a leader is chosen from the out-of-sync replicas, and any messages that were not synced prior to the loss of the former leader are lost forever. Essentially, unclean leader elections sacrifice consistency for availability.

The offline log directory count metric indicate the number of log directories which are offline (due to a hardware failure for example) so that the broker cannot store incoming messages anymore.

Any partition without an active leader will be completely inaccessible, and both consumers and producers of that partition will be blocked until a leader becomes available.

The request handler idle ratio metric indicates the percentage of time the request handlers are not in use. The lower this number, the more loaded the broker is.

The network processor idle ratio metric indicates the percentage of time the network processor are not in use. The lower this number, the more loaded the broker is.

Zabbix has not received data for items for the last 15 minutes

The Under min ISR partitions metric displays the number of partitions, where the number of In-Sync Replicas (ISR) is less than the minimum number of in-sync replicas specified. The two most common causes of under-min ISR partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers are falling behind.

The Under replicated partitions metric displays the number of partitions that do not have enough replicas to meet the desired replication factor. A partition will also be considered under-replicated if the correct number of replicas exist, but one or more of the replicas have fallen significantly behind the partition leader. The two most common causes of under-replicated partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers have fallen behind.

Kafka version has changed. Ack to close.

Manual close: YES

Uptime is less than 10 minutes.

Manual close: YES

-

Filter of discoverable topics

Filter to exclude discovered topics

The minimum Network processor average idle percent for trigger expression.

The minimum Request handler average idle percent for trigger expression.

Number of leader elections per second.

Number of “unclean” elections per second.

Preprocessing

• Change per second

One indicates that the broker is the controller for the cluster.

Preprocessing

• Discard unchanged with heartbeat: 1h

The number of ineligible pending replica deletes.

The number of pending replica deletes.

The number of ineligible pending topic deletes.

The number of pending topic deletes.

The number of offline log directories (for example, after a hardware failure).

Number of partitions that don't have an active leader.

The rate at which data is fetched and read from the broker by consumers.

Preprocessing

• Change per second

The rate at which data sent from producers is consumed by the broker.

Preprocessing

• Change per second

The rate at which individual messages are consumed by the broker.

Preprocessing

• Change per second

The rate at which bytes rejected per second by the broker.

Preprocessing

• Change per second

Number of client fetch request failures per second.

Preprocessing

• Change per second

Number of failed produce requests per second.

Preprocessing

• Change per second

Indicates the percentage of time that the request handler (IO) threads are not in use.

Preprocessing

• Custom multiplier: 100

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time in ms to serve the Fetch-Consumer request.

Time in ms to serve the Fetch-Consumer request for 95th percentile.

Time in ms to serve the specified Fetch-Consumer for 99th percentile.

Average time in ms to serve the Fetch-Follower request.

Time in ms to serve the Fetch-Follower request for 95th percentile.

Time in ms to serve the Fetch-Follower request for 99th percentile.

Average time in ms to serve the Produce request.

Time in ms to serve the Produce requests for 95th percentile.

Time in ms to serve the Produce requests for 99th percentile.

Average time for a request to update metadata.

Time for update metadata requests for 95th percentile.

Time for update metadata requests for 99th percentile.

The maximum of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The maximum of temporary memory used for converting message formats and decompressing messages.

The amount of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The average percentage of time that the network processors are idle.

Preprocessing

• Custom multiplier: 100

Number of requests waiting in producer purgatory.

Number of requests waiting in fetch purgatory.

The maximum lag between the time that messages are received by the leader replica and by the follower replicas.

The number of partitions under the minimum In-Sync Replica (ISR) count.

The number of partitions that have not been fully replicated in the follower replicas (the number of non-reassigning replicas - the number of ISR > 0).

The rate at which the number of ISRs in the broker increases.

Preprocessing

• Change per second

Rate of replicas leaving the ISR pool.

Preprocessing

• Change per second

The number of replicas for which this broker is the leader.

The number of partitions in the broker.

The number of reassigning leader partitions on a broker.

The size of the delay queue.

Current version of broker.

Preprocessing

• Discard unchanged with heartbeat: 1h

The service uptime expressed in seconds.

Preprocessing

• JavaScript: The text is too long. Please see the template.

Latency in milliseconds for ZooKeeper requests from broker.

Connection status of broker's ZooKeeper session.

Preprocessing

• Discard unchanged with heartbeat: 1h

ZooKeeper client disconnect per second.

Preprocessing

• Change per second

ZooKeeper client session expiration per second.

Preprocessing

• Change per second

ZooKeeper client readonly per second.

Preprocessing

• Change per second

ZooKeeper client sync per second.

Preprocessing

• Change per second

Unclean leader elections occur when there is no qualified partition leader among Kafka brokers. If Kafka is configured to allow an unclean leader election, a leader is chosen from the out-of-sync replicas, and any messages that were not synced prior to the loss of the former leader are lost forever. Essentially, unclean leader elections sacrifice consistency for availability.

The offline log directory count metric indicate the number of log directories which are offline (due to a hardware failure for example) so that the broker cannot store incoming messages anymore.

Any partition without an active leader will be completely inaccessible, and both consumers and producers of that partition will be blocked until a leader becomes available.

The request handler idle ratio metric indicates the percentage of time the request handlers are not in use. The lower this number, the more loaded the broker is.

The network processor idle ratio metric indicates the percentage of time the network processor are not in use. The lower this number, the more loaded the broker is.

Zabbix has not received data for items for the last 15 minutes

The Under min ISR partitions metric displays the number of partitions, where the number of In-Sync Replicas (ISR) is less than the minimum number of in-sync replicas specified. The two most common causes of under-min ISR partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers are falling behind.

The Under replicated partitions metric displays the number of partitions that do not have enough replicas to meet the desired replication factor. A partition will also be considered under-replicated if the correct number of replicas exist, but one or more of the replicas have fallen significantly behind the partition leader. The two most common causes of under-replicated partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers have fallen behind.

The Kafka version has changed. Acknowledge to close the problem manually.

Uptime is less than 10 minutes.

The rate at which individual messages are consumed by topic.

Preprocessing

• Change per second

The rate at which data sent from producers is consumed by topic.

Preprocessing

• Change per second

The rate at which data is fetched and read from the broker by consumers (by topic).

Preprocessing

• Change per second

Rejected bytes rate by topic.

Preprocessing

• Change per second

The minimum Network processor average idle percent for trigger expression.

-

The minimum Request handler average idle percent for trigger expression.

Filter of discoverable topics

Filter to exclude discovered topics

-

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

Number of leader elections per second.

Number of “unclean” elections per second.

Preprocessing:

- CHANGE_PER_SECOND

One indicates that the broker is the controller for the cluster.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The number of ineligible pending replica deletes.

The number of pending replica deletes.

The number of ineligible pending topic deletes.

The number of pending topic deletes.

The number of offline log directories (for example, after a hardware failure).

Number of partitions that don't have an active leader.

The rate at which data is fetched and read from the broker by consumers.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which bytes rejected per second by the broker.

Preprocessing:

- CHANGE_PER_SECOND

Number of client fetch request failures per second.

Preprocessing:

- CHANGE_PER_SECOND

Number of failed produce requests per second.

Preprocessing:

- CHANGE_PER_SECOND

Indicates the percentage of time that the request handler (IO) threads are not in use.

Preprocessing:

- MULTIPLIER: 100

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time in ms to serve the Fetch-Consumer request.

Time in ms to serve the Fetch-Consumer request for 95th percentile.

Time in ms to serve the specified Fetch-Consumer for 99th percentile.

Average time in ms to serve the Fetch-Follower request.

Time in ms to serve the Fetch-Follower request for 95th percentile.

Time in ms to serve the Fetch-Follower request for 99th percentile.

Average time in ms to serve the Produce request.

Time in ms to serve the Produce requests for 95th percentile.

Time in ms to serve the Produce requests for 99th percentile.

Average time for a request to update metadata.

Time for update metadata requests for 95th percentile.

Time for update metadata requests for 99th percentile.

The maximum of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The maximum of temporary memory used for converting message formats and decompressing messages.

The amount of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The average percentage of time that the network processors are idle.

Preprocessing:

- MULTIPLIER: 100

Number of requests waiting in producer purgatory.

Number of requests waiting in fetch purgatory.

The maximum lag between the time that messages are received by the leader replica and by the follower replicas.

The number of partitions under the minimum In-Sync Replica (ISR) count.

The number of partitions that have not been fully replicated in the follower replicas (the number of non-reassigning replicas - the number of ISR > 0).

The rate at which the number of ISRs in the broker increases.

Preprocessing:

- CHANGE_PER_SECOND

Rate of replicas leaving the ISR pool.

Preprocessing:

- CHANGE_PER_SECOND

The number of replicas for which this broker is the leader.

The number of partitions in the broker.

The number of reassigning leader partitions on a broker.

The size of the delay queue.

Current version of brocker.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Service uptime in seconds.

Preprocessing:

- JAVASCRIPT: return (Math.floor((Date.now()-Number(value))/1000))

Latency in milliseconds for ZooKeeper requests from broker.

Connection status of broker's ZooKeeper session.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

ZooKeeper client disconnect per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client session expiration per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client readonly per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client sync per second.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data is fetched and read from the broker by consumers (by topic).

Preprocessing:

- CHANGE_PER_SECOND

Rejected bytes rate by topic.

Preprocessing:

- CHANGE_PER_SECOND

Unclean leader elections occur when there is no qualified partition leader among Kafka brokers. If Kafka is configured to allow an unclean leader election, a leader is chosen from the out-of-sync replicas, and any messages that were not synced prior to the loss of the former leader are lost forever. Essentially, unclean leader elections sacrifice consistency for availability.

The offline log directory count metric indicate the number of log directories which are offline (due to an hardware failure for example) so that the broker cannot store incoming messages anymore.

Any partition without an active leader will be completely inaccessible, and both consumers and producers of that partition will be blocked until a leader becomes available.

The request handler idle ratio metric indicates the percentage of time the request handlers are not in use. The lower this number, the more loaded the broker is.

The network processor idle ratio metric indicates the percentage of time the network processor are not in use. The lower this number, the more loaded the broker is.

Zabbix has not received data for items for the last 15 minutes

The Under min ISR partitions metric displays the number of partitions, where the number of In-Sync Replicas (ISR) is less than the minimum number of in-sync replicas specified. The two most common causes of under-min ISR partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers are falling behind.

The Under replicated partitions metric displays the number of partitions that do not have enough replicas to meet the desired replication factor. A partition will also be considered under-replicated if the correct number of replicas exist, but one or more of the replicas have fallen significantly behind the partition leader. The two most common causes of under-replicated partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers have fallen behind.

Kafka version has changed. Ack to close.

Manual close: YES

Uptime is less than 10 minutes

Manual close: YES

-

The minimum Network processor average idle percent for trigger expression.

-

The minimum Request handler average idle percent for trigger expression.

Filter of discoverable topics

Filter to exclude discovered topics

-

-

Filter:

- A: {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- B: {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- A: {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- B: {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

-

Filter:

- A: {#JMXTOPIC} MATCHES_REGEX {$KAFKA.TOPIC.MATCHES}

- B: {#JMXTOPIC} NOT_MATCHES_REGEX {$KAFKA.TOPIC.NOT_MATCHES}

Number of leader elections per second.

Number of “unclean” elections per second.

Preprocessing:

- CHANGE_PER_SECOND

One indicates that the broker is the controller for the cluster.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

The number of ineligible pending replica deletes.

The number of pending replica deletes.

The number of ineligible pending topic deletes.

The number of pending topic deletes.

The number of offline log directories (for example, after a hardware failure).

Number of partitions that don't have an active leader.

The rate at which data is fetched and read from the broker by consumers.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by the broker.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which bytes rejected per second by the broker.

Preprocessing:

- CHANGE_PER_SECOND

Number of client fetch request failures per second.

Preprocessing:

- CHANGE_PER_SECOND

Number of failed produce requests per second.

Preprocessing:

- CHANGE_PER_SECOND

Indicates the percentage of time that the request handler (IO) threads are not in use.

Preprocessing:

- MULTIPLIER: 100

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time taken, in milliseconds, to send the response.

The time taken, in milliseconds, to send the response for 95th percentile.

The time taken, in milliseconds, to send the response for 99th percentile.

Average time in ms to serve the Fetch-Consumer request.

Time in ms to serve the Fetch-Consumer request for 95th percentile.

Time in ms to serve the specified Fetch-Consumer for 99th percentile.

Average time in ms to serve the Fetch-Follower request.

Time in ms to serve the Fetch-Follower request for 95th percentile.

Time in ms to serve the Fetch-Follower request for 99th percentile.

Average time in ms to serve the Produce request.

Time in ms to serve the Produce requests for 95th percentile.

Time in ms to serve the Produce requests for 99th percentile.

Average time for a request to update metadata.

Time for update metadata requests for 95th percentile.

Time for update metadata requests for 99th percentile.

The maximum of temporary memory used for converting message formats and decompressing messages.

The amount of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The maximum of temporary memory used for converting message formats and decompressing messages.

The amount of temporary memory used for converting message formats and decompressing messages.

The minimum of temporary memory used for converting message formats and decompressing messages.

The average percentage of time that the network processors are idle.

Preprocessing:

- MULTIPLIER: 100

Number of requests waiting in producer purgatory.

Number of requests waiting in fetch purgatory.

The maximum lag between the time that messages are received by the leader replica and by the follower replicas.

The number of partitions under the minimum In-Sync Replica (ISR) count.

The number of partitions that have not been fully replicated in the follower replicas (the number of non-reassigning replicas - the number of ISR > 0).

The rate at which the number of ISRs in the broker increases.

Preprocessing:

- CHANGE_PER_SECOND

Rate of replicas leaving the ISR pool.

Preprocessing:

- CHANGE_PER_SECOND

The number of replicas for which this broker is the leader.

The number of partitions in the broker.

The number of reassigning leader partitions on a broker.

The size of the delay queue.

Current version of broker.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

Service uptime in seconds.

Preprocessing:

- JAVASCRIPT: return (Math.floor((Date.now()-Number(value))/1000))

Latency in milliseconds for ZooKeeper requests from broker.

Connection status of broker's ZooKeeper session.

Preprocessing:

- DISCARD_UNCHANGED_HEARTBEAT: 1h

ZooKeeper client disconnect per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client session expiration per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client readonly per second.

Preprocessing:

- CHANGE_PER_SECOND

ZooKeeper client sync per second.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which individual messages are consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data sent from producers is consumed by topic.

Preprocessing:

- CHANGE_PER_SECOND

The rate at which data is fetched and read from the broker by consumers (by topic).

Preprocessing:

- CHANGE_PER_SECOND

Rejected bytes rate by topic.

Preprocessing:

- CHANGE_PER_SECOND

Unclean leader elections occur when there is no qualified partition leader among Kafka brokers. If Kafka is configured to allow an unclean leader election, a leader is chosen from the out-of-sync replicas, and any messages that were not synced prior to the loss of the former leader are lost forever. Essentially, unclean leader elections sacrifice consistency for availability.

The offline log directory count metric indicate the number of log directories which are offline (due to a hardware failure for example) so that the broker cannot store incoming messages anymore.

Any partition without an active leader will be completely inaccessible, and both consumers and producers of that partition will be blocked until a leader becomes available.

The request handler idle ratio metric indicates the percentage of time the request handlers are not in use. The lower this number, the more loaded the broker is.

The network processor idle ratio metric indicates the percentage of time the network processor are not in use. The lower this number, the more loaded the broker is.

Zabbix has not received data for items for the last 15 minutes

The Under min ISR partitions metric displays the number of partitions, where the number of In-Sync Replicas (ISR) is less than the minimum number of in-sync replicas specified. The two most common causes of under-min ISR partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers are falling behind.

The Under replicated partitions metric displays the number of partitions that do not have enough replicas to meet the desired replication factor. A partition will also be considered under-replicated if the correct number of replicas exist, but one or more of the replicas have fallen significantly behind the partition leader. The two most common causes of under-replicated partitions are that one or more brokers is unresponsive, or the cluster is experiencing performance issues and one or more brokers have fallen behind.

Kafka version has changed. Ack to close.

Manual close: YES

Uptime is less than 10 minutes

Manual close: YES

-