[
https://issues.apache.org/jira/browse/FLUME-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal updated FLUME-2550:
----------------------------------
Attachment: FLUME-2550-unstable.patch
Unstable patch for quick review only. Not yet tested. This is 3rd take on
implementing this. Current approach is non-intrusive and can live alongside
exiting monitoring implementation without breaking it. Uploaded the patch for a
quick review and comment on approach. The way it works is
A new monitoring service has been implemented based on Metrics lib, similar to
other implementation. During initialisation, Counters would be registered with
Metrics Registry and exposed as Gauges. The implementation would be exposed as
one more type of monitoring to existing ones. It won't break existing
monitoring solutions.
Remaining TODO's
1. Implement Reporter's to publish Metrics to outside world
2. Write Test Cases
3. And do a dry run
If anyone got some spare cycles, appreciate a quick feedback. I shall try to
publish a working version in a day or so.
> Revamp Metrics reporting to use CodaHale Metrics package
> --------------------------------------------------------
>
> Key: FLUME-2550
> URL: https://issues.apache.org/jira/browse/FLUME-2550
> Project: Flume
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: v1.5.0
> Reporter: Ashish Paliwal
> Assignee: Ashish Paliwal
> Attachments: FLUME-2550-unstable.patch
>
>
> Use CodaHale Metrics package to revamp current Metrics reporting system. This
> shall help provide lot more information around our existing Metrics
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
