[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-06-16 Thread Richard Wagner (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-06-12 Thread Yuki Morishita (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14030020#comment-14030020
 ] 

Yuki Morishita commented on CASSANDRA-6539:
---

+1

 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

 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-06-10 Thread Yuki Morishita (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026740#comment-14026740
 ] 

Yuki Morishita commented on CASSANDRA-6539:
---

You need to instantiate KeyspaceMetrics object at Keyspace creation and 
discard(release) when it closed. Otherwise metrics won't show up.

I honestly don't get the point of trying to aggregate all metrics from CF. 
Total memtable/SSTable/BF sizes are fine, but I don't think others like max row 
size/latency/BF fp ratio are not so much.

 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

 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-06-09 Thread Brandon Williams (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025764#comment-14025764
 ] 

Brandon Williams commented on CASSANDRA-6539:
-

WDYT [~yukim]?

 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

 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-05-30 Thread Brandon Williams (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014351#comment-14014351
 ] 

Brandon Williams commented on CASSANDRA-6539:
-

I also did not reach into internals for anything purposefully, but instead 
built on the cf metrics in an effort to hopefully keep future maintenance 
localized there.

 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
 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-03-14 Thread Nick Bailey (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935320#comment-13935320
 ] 

Nick Bailey commented on CASSANDRA-6539:


It's just slightly easier to do it in C*. The metrics library does nice things 
like automatically expose the metric data in multiple ways. And like I said, in 
the case of huge numbers of column families (thousands and above), it's less 
burdensome to do the aggregation in C* than on the client.

 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
Priority: Minor
  Labels: lhf

 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-03-13 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934589#comment-13934589
 ] 

Jonathan Ellis commented on CASSANDRA-6539:
---

I'm not sure why having C* do the aggregation is better than having a 
monitoring service do it.

 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
Priority: Minor
  Labels: lhf

 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)


[jira] [Commented] (CASSANDRA-6539) Track metrics at a keyspace level as well as column family level

2014-01-02 Thread Nick Bailey (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860631#comment-13860631
 ] 

Nick Bailey commented on CASSANDRA-6539:


To be a bit clearer, this is more useful for data models and clusters where 
there are a very large amount of column families per keyspace (hundreds or 
thousands). Tracking only individual column families can be burdensome at that 
level.

 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: Bug
Reporter: Nick Bailey

 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.1.5#6160)