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

Chris Lohfink commented on CASSANDRA-7273:
------------------------------------------

bq. Aggregated histograms can be misleading

Whys that? higher rate of inserts does shorten the window when using exp. 
decaying reservoir but its ultimately the same as say - the client request 
metrics.  I didn't merge the histograms, I created a new ones and replicated 
all the updates to them.  Some of those histograms would be really helpful too. 
 ie things like sstables per read and tombstones would be huge win for me 
personally when reviewing a new cluster so I can retire a bunch of fabric 
scripts.

> expose global ColumnFamily metrics
> ----------------------------------
>
>                 Key: CASSANDRA-7273
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7273
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Richard Wagner
>            Assignee: Brandon Williams
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.2.17
>
>         Attachments: 7273-2_1_branch-v1.txt
>
>
> It would be very useful to have cassandra expose ColumnFamily metrics that 
> span all column families. A general purpose cassandra monitoring system built 
> up around the current ColumnFamily metrics really only has a couple of 
> choices right now: publish metrics for all column families or fetch metrics 
> for all column families, aggregate them and then publish the aggregated 
> metrics. The first can be quite expensive for the downstream monitoring 
> system and the second is a piece of work that it seems is better pushed into 
> cassandra itself.
> Perhaps these global ColumnFamily metrics could be published under a name of:
> org.apache.cassandra.metrics:type=(ColumnFamily|IndexColumnFamily),name=(Metric
>  name)
> (Same as existing ColumnFamily metrics, but with no keyspace or scope.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to