[jira] [Commented] (CASSANDRA-4430) optional pluggable o.a.c.metrics reporters

["Chris Burroughs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500282#comment-13500282 ] 

Chris Burroughs commented on CASSANDRA-4430:
--------------------------------------------

https://github.com/addthis/metrics-reporter-config <-- library, needs integration
                
> optional pluggable o.a.c.metrics reporters
> ------------------------------------------
>
>                 Key: CASSANDRA-4430
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4430
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Burroughs
>            Priority: Minor
>
> CASSANDRA-4009  expanded the use of the metrics library which has a set of reporter modules http://metrics.codahale.com/manual/core/#reporters  You can report to flat files, ganglia, spit everything over http, etc.  The next step is a mechanism for using those reporters with  o.a.c.metrics.  To avoid bundling everything I suggest following the mx4j approach of "enable only if on classpath coupled with a reporter configuration file.
> Strawman file:
> {noformat}
> console:
>   time: 1
>   timeunit: "seconds"
> csv:
>  - time: 1
>    timeunit: minutes
>    file: foo.csv
>  - time: 10
>    timeunit: seconds
>     file: bar.csv
> ganglia:
>  - time: 30
>    timunit: seconds
>    host: server-1
>    port: 8649
>  - time: 30
>    timunit: seconds
>    host: server-2
>    port: 8649
> {noformat}
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira