THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Name | Context | Type | Description |
|---|---|---|---|
kafka.controller:type=KafkaController,name=TimedOutBrokerHeartbeatCount | Controller | Long | The number of broker heartbeats that timed out on this controller since the process was started. Note that only active controllers handle heartbeats, so only they will see increases in this metric. |
kafka.controller:type=KafkaController,name=EventQueueOperationsPerformedCount | Controllers | Long | The total number of event queue operations that were performed. This includes deferred operations. |
kafka.controller:type=KafkaController,name=EventQueueOperationsTimedOutCount | Controllers | Long | The total number of event queue operations that timed out before they could be performed. |
kafka.controller:type=KafkaController,name=NewActiveControllersCount | Controller | Long | Counts the number of times this node has seen a new controller elected. A transition to the "no leader" state is not counted here. If the same controller as before becomes active, that still counts. |
kafka.server:type=MetadataLoader,name=CurrentMetadataVersion | Broker and Controller | Integer | Outputs the feature level of the current effective metadata version as an integer value. |
kafka.server:type=MetadataLoader,name=HandleLoadSnapshotCount | Broker and Controller | Long | The total number of times we have loaded a KRaft snapshot since the process was started. |
kafka.server:type=MetadataLoader,name=LatestSnapshotGeneratedBytes | Broker and Controller | Long | The total size in bytes of the latest snapshot that the node has generated, or 0 if there hasn't been one yet. |
kafka.server:type=MetadataLoader,name=LatestSnapshotGeneratedAgeMs | Broker and Controller | Long | The interval in miliseconds since the latest snapshot that the node has generated, or 0 if there hasn't been one yet. |
...
This metric simply reflects the current metadata version. It comes from the numeric "feature level" of the metadata version. It is useful for administrators with multiple clusters, who want to ensure that they're all up-to-date. It also is helpful to know at a glance when a metadata version transition occurred.
...