Copilot commented on code in PR #22684:
URL: https://github.com/apache/kafka/pull/22684#discussion_r3627742445
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
Review Comment:
The metric name here does not match the actual exported metric (Kafka
exports `time-between-network-thread-poll-avg` and
`time-between-network-thread-poll-max`, not a bare
`time-between-network-thread-poll`). This makes the documentation inaccurate
and harder to query via JMX.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that background events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-processing-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that the consumer took to process all
available background events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+unsent-requests-queue-size
+</td>
+<td>
+
+The current number of unsent requests in the consumer network (for CONSUMER
protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+unsent-requests-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that requests are taking to be sent in the
consumer network (for CONSUMER protocol)
Review Comment:
This description refers to the "consumer network", but the metric tracks
time in the background thread (per the metric’s definition). Aligning the
wording avoids confusion when interpreting the metric.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that background events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that background events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-processing-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that the consumer took to process all
available background events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that background events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-processing-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that the consumer took to process all
available background events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+unsent-requests-queue-size
+</td>
+<td>
+
+The current number of unsent requests in the consumer network (for CONSUMER
protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+unsent-requests-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that requests are taking to be sent in the
consumer network (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
Review Comment:
This description says "maximum" but the metric name is `...-avg`. The
wording should describe the average, and it should align with the metric’s
meaning (background thread processing application events).
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
##########
docs/operations/monitoring.md:
##########
@@ -3446,8 +3446,139 @@ The total time the Consumer spent committing offsets in
nanoseconds (for AOS).
</td>
<td>
-kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
-</td> </tr> </table>
+kafka.consumer:type=consumer-metrics,client-id=([-.\w]+)
+</td> </tr>
+<tr>
+<td>
+
+time-between-network-thread-poll</td>
+<td>
+
+The average delay between invocations of poll (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td> </tr>
+<tr>
+<td>
+
+application-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer network application event queue
(for CONSUMER protocol).
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that application events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-event-queue-processing-time-avg
+</td>
+<td>
+
+The maximum time, in milliseconds, that the consumer network took to process
all available application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+application-events-expired-count
+</td>
+<td>
+
+The current number of expired application events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-size
+</td>
+<td>
+
+The current number of events in the consumer background event queue (for
CONSUMER protocol)
+</td>
+
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that background events are taking to be
dequeued (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+background-event-queue-processing-time-avg
+</td>
+<td>
+
+The average time, in milliseconds, that the consumer took to process all
available background events (for CONSUMER protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
+</td></tr>
+<tr>
+<td>
+
+unsent-requests-queue-size
+</td>
+<td>
+
+The current number of unsent requests in the consumer network (for CONSUMER
protocol)
+</td>
+<td>
+
+kafka.consumer:type=consumer-metrics,client-id={clientId}
Review Comment:
This section uses `client-id={clientId}`, but the surrounding Consumer
Metrics table documents MBeans using a regex pattern (e.g.,
`client-id=([-\.\w]+)` at docs/operations/monitoring.md:3423). For consistency
with the rest of the table, use the same pattern here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
