[
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033263#comment-14033263
]
Richard Wagner commented on CASSANDRA-6539:
-------------------------------------------
I think it is actually quite useful to have ALL the ColumnFamily metrics
aggregated up to the keyspace level (and then up to the global level per
CASSANDRA-7273). Much in the way that we have a complete set of metrics
available at the StorageProxy level - including latencies - that are across all
keyspaces and column families, these metrics are quite useful in general at the
storage node level. In our case, we have a downstream monitoring cluster that
we send metrics to. To build a generic, multi-tenant monitoring solution we
have to either 1) aggregate all the CF metrics and present a "global" set of
metrics or 2) capture metrics for ALL column families for all tenants. 2) is
prohibitively expensive for us. Especially considering the small incremental
benefit we see in practice from having this information broken down to the
specific CF level. Almost always, we can diagnose issues with a global CF view
of metrics. But going with solution 1), it is important that we get access to
all the metrics.
The way I think of it, conceptually, you could have 3 complete and identical
sets of metrics widgets instantiated: CF, Keyspace and Global. Every time
something measurable happens, you adjust the corresponding metric widget at all
3 levels.
> Track metrics at a keyspace level as well as column family level
> ----------------------------------------------------------------
>
> Key: CASSANDRA-6539
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6539
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Nick Bailey
> Assignee: Brandon Williams
> Priority: Minor
> Labels: lhf
> Fix For: 1.2.17, 2.0.9, 2.1 rc2
>
> Attachments: 6539-1.2.txt, 6539-2.0.txt
>
>
> It would be useful to be able to see aggregated metrics (write/read
> count/latency) at a keyspace level as well as at the individual column family
> level.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
