[
https://issues.apache.org/jira/browse/FLUME-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221791#comment-14221791
]
Ashish Paliwal commented on FLUME-2562:
---------------------------------------
IMHO we need to make some functions in MonitoredCounterGroup visible to using
classes (extended classes internally use them). For JMX, we can expose the
counterMap using DynamicMBean or some other way.
CounterGroup class is used across the code (19 usage), may be we can either
plugin the code into Metrics system or phase it out.
> 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
>
> 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)
