[ https://issues.apache.org/jira/browse/CASSANDRA-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605956#comment-13605956 ]
Chris Burroughs commented on CASSANDRA-4430: -------------------------------------------- bq. Can you clarify which stats you're referring to? I didn't think we were exposing any metrics on a per-connection basis. See the per connection ones in http://wiki.apache.org/cassandra/Metrics ; fox example per IP ones in StreamingMetrics https://github.com/apache/cassandra/blob/cassandra-1.2.3/src/java/org/apache/cassandra/metrics/StreamingMetrics.java. I just mean that as an example of something that generates too much noise to be a good out of the box experience. bq. Is the csv reporter just no good, or am I missing something here? The csv reporter is probably not used in production much. I'm not exactly sure what is going on when trying to use it here, but I agree it's producing a paucity of metrics. bq. Regarding whitelisting/blacklisting, is the regex applied to the full metric name (e.g. o.a.c.metrics.ColumnFamily.WriteLatency.keyspace1.cf1)? Currently only the "name" part of MetricName (so "LiveSSTableCount" not "org.apache.cassandra.metrics.ColumnFamily.LiveSSTableCount.system.IndexInfo") is used. However, that's a metric-reporter-config limitation, not a Metrics one, and could be changed. a.o.c.metrics has a rather sophisticated naming scheme and I'm not sure how best to keep it simple. > 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 > Assignee: Chris Burroughs > Priority: Minor > Fix For: 1.2.4 > > 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