You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/09/16 20:30:34 UTC

[jira] [Reopened] (CASSANDRA-7719) Add PreparedStatements related metrics

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

Aleksey Yeschenko reopened CASSANDRA-7719:
------------------------------------------

Reopening, because of stuff like CASSANDRA-7930, and CASSANDRA-7921 depending on it.

> Add PreparedStatements related metrics
> --------------------------------------
>
>                 Key: CASSANDRA-7719
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7719
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Michaël Figuière
>            Assignee: T Jake Luciani
>            Priority: Minor
>             Fix For: 2.1.1
>
>         Attachments: 7719.txt
>
>
> Cassandra newcomers often don't understand that they're expected to use PreparedStatements for almost all of their repetitive queries executed in production.
> It doesn't look like Cassandra currently expose any PreparedStatements related metrics.It would be interesting, and I believe fairly simple, to add several of them to make it possible, in development / management / monitoring tools, to show warnings or alerts related to this bad practice.
> Thus I would suggest to add the following metrics:
> * Executed prepared statements count
> * Executed unprepared statements count
> * Amount of PreparedStatements that have been registered on the node



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