cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4430) optional pluggable o.a.c.metrics reporters
Date Wed, 28 Aug 2013 22:34:52 GMT

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

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

New draft up !
https://github.com/cburroughs/cassandra/tree/metrics-config-2, uses metrics-report-config
SNAPSHOT with "qualified" names (org.apache.cassandra.metrics.ClientRequest...)

 * Rebased against latest 1.2 branch. I'm running 1.2 and hope to have this on my production
clusters soon.
 * Added a sample file that sends all global (not good terminology, as in metrics that are
not per connection/columFamily) to a file
 * Didn't like hard coding in bin/cassandra so -Dcassandra.metricsReporterConfigFile must
be specified for this to do anything

CSVReporter only works if the non-qualifed names are unique.  The same uses the console reporter
to dump everything to one big file which is really only useful as a sample
                
> 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: 2.1
>
>         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

Mime
View raw message