Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Wed, 4 Oct 2017 18:18:00 +0000 (UTC)
From: "Ewen Cheslack-Postava (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13107018.1507141059000.272543.1507141080514@Atlassian.JIRA>
In-Reply-To: <JIRA.13107018.1507141059000@Atlassian.JIRA>
References: <JIRA.13107018.1507141059000@Atlassian.JIRA> <JIRA.13107018.1507141059967@jira-lw-us.apache.org>
Subject: [jira] [Created] (KAFKA-6011) AppInfoParser should only use metrics
 API and should not register JMX mbeans directly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 Oct 2017 18:18:05 -0000

Ewen Cheslack-Postava created KAFKA-6011:
--------------------------------------------

             Summary: AppInfoParser should only use metrics API and should not register JMX mbeans directly
                 Key: KAFKA-6011
                 URL: https://issues.apache.org/jira/browse/KAFKA-6011
             Project: Kafka
          Issue Type: Bug
          Components: metrics
            Reporter: Ewen Cheslack-Postava
            Priority: Minor


AppInfoParser collects info about the app ID, version, and commit ID and logs them + exposes corresponding metrics. For some reason we ended up with the app ID metric being registered directly to JMX while the version and commit ID use the metrics API. This means the app ID would not be accessible to custom metrics reporter.

This isn't a huge loss as this is probably a rarely used metric, but we should really only be using the metrics API. Only using the metrics API would also reduce and centralize the places we need to do name mangling to handle characters that might not be valid for metrics.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)