[jira] [Comment Edited] (CASSANDRA-7384) Collect metrics on queries by consistency level

[Robert Stupp (JIRA)]

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

Robert Stupp edited comment on CASSANDRA-7384 at 7/15/16 5:19 AM:
--

Generally LGTM - just a one comment:
* we use {{.}} as a separator throughout the metrics. Would be nicer to use a 
{{.}} instead of {{\-}} for the metric names (in the constructor initializing 
the metric maps - e.g. {{new ClientRequestMetrics("Read-" + level.name())}})

If you're fine, I can fix that on commit.


was (Author: snazy):
Generally LGTM - just a one comment:
* we use {{.}} as a separator throughout the metrics. Would be nicer to use a 
{{.}} instead of {{-}} for the metric names (in the constructor initializing 
the metric maps - e.g. {{new ClientRequestMetrics("Read-" + level.name())}})

If you're fine, I can fix that on commit.

> Collect metrics on queries by consistency level
> ---
>
> Key: CASSANDRA-7384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7384
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Vishy Kasar
>Assignee: sankalp kohli
>Priority: Minor
> Fix For: 3.x
>
> Attachments: CASSANDRA-7384_3.0_v2.txt
>
>
> We had cases where cassandra client users thought that they were doing 
> queries at one consistency level but turned out to be not correct. It will be 
> good to collect metrics on number of queries done at various consistency 
> level on the server. See the equivalent JIRA on java driver: 
> https://datastax-oss.atlassian.net/browse/JAVA-354



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CASSANDRA-7384) Collect metrics on queries by consistency level

[Or Sher (JIRA)]

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

Or Sher edited comment on CASSANDRA-7384 at 8/7/14 1:58 PM:


I would be happy to have such metrics, I would even sample count and latency 
per column family and per CL.
We have many applications using the same shared clusters.
Many developers from different teams are working with different APIs (Hector  
CQL3), and with different standards and wrappers.
As the DBA, I'm not able to verify that each project is using the CL it thinks 
or need to use. That would really help me out and I'm sure it also help many 
other companies where the administration and development have different owners.
Comparing the read/write latency for different CL on run time in our production 
cluster would also be a great value.


was (Author: or.sher1):
I would be happy to have such metrics, I would even sample count and latency 
per column family and per CL.
We have many applications using the same shared clusters.
Many developers from different teams are working with different APIs (Hector  
CQL3), and with different standards and wrappers.
As the DBA, I'm not able to verify that each project is using the CL it thinks 
or need to. That would really help me out and I'm sure it also help many other 
companies where the administration and development have different owners.
Comparing the read/write latency for different CL on run time in our production 
cluster would also be a great value.

 Collect metrics on queries by consistency level
 ---

 Key: CASSANDRA-7384
 URL: https://issues.apache.org/jira/browse/CASSANDRA-7384
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Vishy Kasar
Assignee: sankalp kohli
Priority: Minor
 Fix For: 2.0.10


 We had cases where cassandra client users thought that they were doing 
 queries at one consistency level but turned out to be not correct. It will be 
 good to collect metrics on number of queries done at various consistency 
 level on the server. See the equivalent JIRA on java driver: 
 https://datastax-oss.atlassian.net/browse/JAVA-354



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