[
https://issues.apache.org/jira/browse/FLUME-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220843#comment-14220843
]
Ashish Paliwal commented on FLUME-2562:
---------------------------------------
AFAIK, no direct way of testing this. These metrics cannot be exposed via JMX
or by other means, as they rely on JMX internally (meaning we could reuse
existing test cases). One way I can think of is to get hold of counterGroup and
then asserting on it. Spring has ReflectionTestUtils, there might be something
similar in junit as well
> 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.0.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)
