[
https://issues.apache.org/jira/browse/KAFKA-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725596#comment-15725596
]
ASF GitHub Bot commented on KAFKA-3537:
---------------------------------------
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/2215
KAFKA-3537: Expose metrics registry
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka
KAFKA-3537-access-low-level-metrics
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2215.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2215
----
commit f212c3630dfbaf0c666a5e78d095d20776065bef
Author: Eno Thereska <eno.there...@gmail.com>
Date: 2016-12-06T14:14:01Z
Expose metrics registry
----
> Provide access to low-level Metrics in ProcessorContext
> -------------------------------------------------------
>
> Key: KAFKA-3537
> URL: https://issues.apache.org/jira/browse/KAFKA-3537
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 0.9.0.1
> Reporter: Michael Coon
> Assignee: Eno Thereska
> Priority: Minor
> Labels: semantics
> Fix For: 0.10.2.0
>
>
> It would be good to have access to the underlying Metrics component in
> StreamMetrics. StreamMetrics forces a naming convention for metrics that does
> not fit our use case for reporting. We need to be able to convert the stream
> metrics to our own metrics formatting and it's cumbersome to extract group/op
> names from pre-formatted strings the way they are setup in StreamMetricsImpl.
> If there were a "metrics()" method of StreamMetrics to give me the underlying
> Metrics object, I could register my own sensors/metrics as needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
