Manan Gupta created KAFKA-21016:
-----------------------------------
Summary: Add quota-utilization metric for client quotas
Key: KAFKA-21016
URL: https://issues.apache.org/jira/browse/KAFKA-21016
Project: Kafka
Issue Type: Task
Reporter: Manan Gupta
Assignee: Manan Gupta
Brokers expose per-client quota usage (byte-rate, request-time) and
throttle-time, but not how that usage compares to the quota actually applied to
the same sensor. Operators have to resolve user, client-id, and default
overrides (or a custom ClientQuotaCallback) out of band and join it to the
scraped rate. Because quota limits vary by orders of magnitude and can change
dynamically, absolute-rate alerts do not transfer across clients, and
throttle-time only moves after a violation has already happened.
This ticket adds a quota-utilization attribute to the existing client-quota
MBeans:
{code:java}
quota-utilization = measured-rate / effective-quota * 100{code}
{code:java}
kafka.server:type=Produce,user=...,client-id=... (numerator: byte-rate)
kafka.server:type=Fetch,user=...,client-id=... (numerator: byte-rate)
kafka.server:type=Request,user=...,client-id=... (numerator: request-time){code}
No new MBean type, ObjectName, sensor, or quota entity is introduced. This is
an additional attribute on the sensors that already exist.
[KIP-1373: Client Quota Utilization
Metrics|https://cwiki.apache.org/confluence/x/tojwGg]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
