You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Andras Sereny (JIRA)" <ji...@apache.org> on 2015/05/05 12:59:00 UTC

[jira] [Comment Edited] (KAFKA-2156) Possibility to plug in custom MetricRegistry

    [ https://issues.apache.org/jira/browse/KAFKA-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528203#comment-14528203 ] 

Andras Sereny edited comment on KAFKA-2156 at 5/5/15 10:58 AM:
---------------------------------------------------------------

Thanks Neha. This might already work with Kafka Metrics, as far as I can see: get the appropriate Sensors from the Metrics (this has to be accessible somehow) and then .add a custom MeasurableStat to the Sensor. Not too elegant (have to get all the necessary Sensors), but workable. Is there a timeline for migarting to Kafka Metrics? Thanks, András 


was (Author: sandris):
Thanks Neha. This might already work with Kafka Metrics, as far as I can see: get the appropriate Sensors from the Metrics (this has to be accessible somehow) and then .add a custom MeasurableStat to the Sensor. Not too elegant (have to get all the necessary Sensors), but workable. Is there a timeline for converting to Kafka Metrics? Thanks, András 

> Possibility to plug in custom MetricRegistry
> --------------------------------------------
>
>                 Key: KAFKA-2156
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2156
>             Project: Kafka
>          Issue Type: Improvement
>          Components: producer 
>    Affects Versions: 0.8.1.2
>            Reporter: Andras Sereny
>            Assignee: Jun Rao
>
> The trait KafkaMetricsGroup refers to Metrics.defaultRegistry() throughout. It would be nice to be able to inject any MetricsRegistry instead of the default one. 
> (My usecase is that I'd like to channel Kafka metrics into our application's metrics system, for which I'd need custom implementations of com.yammer.metrics.core.Metric.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)