[
https://issues.apache.org/jira/browse/CASSANDRA-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127922#comment-14127922
]
Mikhail Stepura commented on CASSANDRA-7719:
--------------------------------------------
Couple of nits,
* Don't use {{String.format}} in {{logger.trace}}, use parameterized messages.
Like {code}logger.trace("Stored prepared statement {} with {} bind markers",
statementId, prepared.statement.getBoundTerms()){code}
* Replace Java {{assert}} with appropriate methods from {{org.junit.Assert}}.
> 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)
