You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/04/11 21:18:25 UTC

[jira] [Updated] (KAFKA-3537) Provide access to low-level Metrics in ProcessorContext

     [ https://issues.apache.org/jira/browse/KAFKA-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang updated KAFKA-3537:
---------------------------------
    Fix Version/s: 0.10.1.0

> 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: Guozhang Wang
>            Priority: Minor
>              Labels: semantics
>             Fix For: 0.10.1.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)