[
https://issues.apache.org/jira/browse/FLUME-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225586#comment-14225586
]
Ashish Paliwal commented on FLUME-2562:
---------------------------------------
[~gwenshap] Can we find a generic way to expose the Counters? Extending
Counters for each specific class would be a lot of boiler plate code. The
extended classes have one of the change needed. This is good to support any
number of Counters. Only thing needed is change in JMX infra to expose this. Or
we can commit this and later generalise the changes. The codahale patch I am
working on follows the same path. So if this goes early, I would like to rebase
the patch.
> Metrics for Flafka components
> -----------------------------
>
> Key: FLUME-2562
> URL: https://issues.apache.org/jira/browse/FLUME-2562
> Project: Flume
> Issue Type: Improvement
> Reporter: Gwen Shapira
> Assignee: Gwen Shapira
> Attachments: FLUME-2562.1.patch
>
>
> Kafka source, sink and channel should have metrics. This will help us track
> down possible issues or performance problems.
> Here are the metrics I came up with:
> kafka.next.time - Time spent waiting for events from Kafka (source and
> channel)
> kafka.send.time - Time spent sending events (channel and sink)
> kafka.commit.time - Time spent committing (source and channel)
> events.sent - Number of events sent to Kafka (sink and channel)
> events.read - Number of events read from Kafka (channel and source)
> events.rollback - Number of event rolled back (channel) or number of rollback
> calls (sink)
> kafka.empty - Number of times backing off due to empty kafka topic (source)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
