cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4430) optional pluggable o.a.c.metrics reporters
Date Tue, 19 Mar 2013 22:21:16 GMT

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

Tyler Hobbs commented on CASSANDRA-4430:
----------------------------------------

bq. 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.

I feel like this is probably the main problem that needs to be solved.  Besides per-connection
metrics (thanks for pointing those out), there are many users with hundreds or thousands of
column families, each of which have quite a few metrics.  Ideally, it would be easy to:
1. Capture all metrics for only a specific column family
2. Capture only one specific metric (e.g. read latency) across all column families

It seems like the regex support should be sufficient for that if it's applied to the full
metric name (o.a.c.metrics.ColumnFamily.LiveSSTableCount.system.IndexInfo). How hard would
it be to make changes to metric-reporter-config to support using the full metric name?
                
> 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

Mime
View raw message