DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Table of Contents |
|---|
Status
Current state: Under Discussion Approved
Discussion thread: here
Vote thread: here
JIRA: Jira server ASF JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-15186
Motivation
All Kafka components register AppInfo metrics to track application details such as start time and commit-id etc. These metrics are valuable for monitoring and debugging. However, AppInfo does not include the client-id for Worker and MM2 clients, which is an important piece of information for custom metrics reporters. While most Kafka clients (consumer, producer, admin) already register their client-id in the metrics config, there are cases in MM2 and Worker where AppInfo is registered without the client-id.
The AppInfoParser class registers a JMX MBean with the provided client-id, but when adding metrics to the Metrics registry, the client-id is not included. This KIP proposes adding the client-id as a metric tag.
Public Interfaces
Currently MetricName for Worker and MM2 clients:
...