[ https://issues.apache.org/jira/browse/CASSANDRA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605161#comment-13605161 ]
Chris Burroughs commented on CASSANDRA-4430: -------------------------------------------- Rebased to 1.2.3 without trouble (although I think snakeyaml is going to force this to be a 2.0 feature), and we have been running with this in a per-production environment without incident. Keeping per connection stats around is not tenable for larger clusters, so I think we will need a default config with an example blacklist (what we do with internal services is a convention like ending metric names with JMX_ONLY, but that's probably too ugly and brittle for general use). What I need at this point is: * feedback on the configuration approach bin/cassandra referenced system property * Are the transitive deps okay? > 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 > Attachments: cassandra-ganglia-example.png > > > 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