You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/18 18:13:03 UTC

[jira] [Updated] (CASSANDRA-9520) Track per statement metrics for select prepared statements

     [ https://issues.apache.org/jira/browse/CASSANDRA-9520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-9520:
----------------------------------------
    Component/s: Metrics

> 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
>          Components: Metrics
>            Reporter: Aleksey Yeschenko
>            Priority: Major
>              Labels: client-impacting, metrics
>             Fix For: 4.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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org