[
https://issues.apache.org/jira/browse/CASSANDRA-7273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033926#comment-14033926
]
Yuki Morishita commented on CASSANDRA-7273:
-------------------------------------------
First of all, thanks Chris for taking a look at this one.
I'm not a fan of aggregating all CF metrics to global level (as I pointed out
in CASSANDRA-6539).
Aggregated histograms can be misleading, we already have node-level latency
metrics, etc.
I think the way to do here is just sum Keyspace metrics.
{quote}
* tried to automate some of the releasing of metrics since seems error prone
(WaitingOnFreeMemtableSpace was missing).
* renamed MemtableHeapSize since there were 2 metrics with that name
{quote}
Thanks for pointing these out. I noticed there are some release/naming problem
in CF metrics.
I will fix these in separate commit.
> 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)
