[
https://issues.apache.org/jira/browse/KAFKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15306230#comment-15306230
]
ASF GitHub Bot commented on KAFKA-3715:
---------------------------------------
GitHub user aartigupta opened a pull request:
https://github.com/apache/kafka/pull/1446
Kafka Streams: add granular metrics per node
Kafka Streams: add granular metrics per node, also expose ability to …
…register non latency metrics in StreamsMetrics
from https://github.com/apache/kafka/pull/1362#issuecomment-218326690-------
We can consider adding metrics for process / punctuate / commit rate at the
granularity of each processor node in addition to the global rate mentioned
above. This is very helpful in debugging.
We can consider adding rate / total cumulated metrics for context.forward
indicating how many records were forwarded downstream from this processor node
as well. This is helpful in debugging.
We can consider adding metrics for each stream partition's timestamp.
This is helpful in debugging.
Besides the latency metrics, we can also add throughput latency in terms of
source records consumed.
--------------
More discussions here https://issues.apache.org/jira/browse/KAFKA-3715
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aartigupta/kafka trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1446.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 #1446
----
commit 05b0947c333445024dd3924659302bba65b4cd85
Author: aartigupta <aartigup...@gmail.com>
Date: 2016-05-30T03:42:43Z
Kafka Streams: add granular metrics per node, also expose ability to
register non latency metrics in StreamsMetrics
From https://github.com/apache/kafka/pull/1362#issuecomment-218326690
We can consider adding metrics for process / punctuate / commit rate at the
granularity of each processor node in addition to the global rate mentioned
above. This is very helpful in debugging.
We can consider adding rate / total cumulated metrics for context.forward
indicating how many records were forwarded downstream from this processor node
as well. This is helpful in debugging.
We can consider adding metrics for each stream partition's timestamp.
This is helpful in debugging.
Besides the latency metrics, we can also add throughput latency in terms of
source records consumed.
More discussions here https://issues.apache.org/jira/browse/KAFKA-3715
commit dbaad2a54cf103f7420304f7c5768eda36bfa750
Author: aartigupta <aartigup...@gmail.com>
Date: 2016-05-30T04:57:55Z
Kafka Streams: add granular metrics per node, also expose ability to
register non latency metrics in StreamsMetrics
From https://github.com/apache/kafka/pull/1362#issuecomment-218326690
We can consider adding metrics for process / punctuate / commit rate at the
granularity of each processor node in addition to the global rate mentioned
above. This is very helpful in debugging.
We can consider adding rate / total cumulated metrics for context.forward
indicating how many records were forwarded downstream from this processor node
as well. This is helpful in debugging.
We can consider adding metrics for each stream partition's timestamp.
This is helpful in debugging.
Besides the latency metrics, we can also add throughput latency in terms of
source records consumed.
More discussions here https://issues.apache.org/jira/browse/KAFKA-3715
----
> Higher granularity streams metrics
> -----------------------------------
>
> Key: KAFKA-3715
> URL: https://issues.apache.org/jira/browse/KAFKA-3715
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Jeff Klukas
> Assignee: aarti gupta
> Priority: Minor
> Labels: api, newbie
> Fix For: 0.10.1.0
>
>
> Originally proposed by [~guozhang] in
> https://github.com/apache/kafka/pull/1362#issuecomment-218326690
> We can consider adding metrics for process / punctuate / commit rate at the
> granularity of each processor node in addition to the global rate mentioned
> above. This is very helpful in debugging.
> We can consider adding rate / total cumulated metrics for context.forward
> indicating how many records were forwarded downstream from this processor
> node as well. This is helpful in debugging.
> We can consider adding metrics for each stream partition's timestamp. This is
> helpful in debugging.
> Besides the latency metrics, we can also add throughput latency in terms of
> source records consumed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
