You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Nikolay Izhikov (JIRA)" <ji...@apache.org> on 2018/12/11 05:47:00 UTC

[jira] [Commented] (KAFKA-6820) Improve on StreamsMetrics Public APIs

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

Nikolay Izhikov commented on KAFKA-6820:
----------------------------------------

Hello, [~vvcephei]

Is this ticket still actual?
I want to pick up it.

> Improve on StreamsMetrics Public APIs
> -------------------------------------
>
>                 Key: KAFKA-6820
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6820
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Guozhang Wang
>            Priority: Major
>              Labels: needs-kip
>
> Our current `addLatencyAndThroughputSensor`, `addThroughputSensor` are not very well designed and hence not very user friendly to people to add their customized sensors. We could consider improving on this feature. Some related things to consider:
> 1. Our internal built-in metrics should be independent on these public APIs which are for user customized sensor only. See KAFKA-6819 for related description.
> 2. We could enforce the scopeName possible values, and well document on the sensor hierarchies that would be incurred from the function calls. In this way the library can help closing user's sensors automatically when the corresponding scope (store, task, thread, etc) is being de-constructed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)