[
https://issues.apache.org/jira/browse/CASSANDRA-9520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567883#comment-14567883
]
Matt Stump commented on CASSANDRA-9520:
---------------------------------------
It would be useful, but I view it as a sub-class of problem solved by
CASSANDRA-9193. I'de rather have a more general toolkit that can solve a broad
class of problems caused by lack of visibility than have a collection of single
purpose tools.
> Track per statement metrics for select prepared statements
> ----------------------------------------------------------
>
> Key: CASSANDRA-9520
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9520
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Labels: client-impacting, metrics
> Fix For: 3.x
>
>
> It would be nice to provide users with more granular metrics for the queries
> they want to measure.
> I suggest extending the native protocol to allow setting an extra flag that
> would indicate whether or not the statement should have its own separate
> metrics, and measure latency and counts for each such statement individually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
