Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 8 Aug 2014 00:50:15 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12732709.1407450746787.39438.1407459015910@arcas>
In-Reply-To: <JIRA.12732709.1407450746787@arcas>
References: <JIRA.12732709.1407450746787@arcas>
Subject: [jira] [Updated] (CASSANDRA-7719) Add PreparedStatements related
 metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-7719?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-7719:
--------------------------------------

    Assignee: T Jake Luciani

> Add PreparedStatements related metrics
> --------------------------------------
>
>                 Key: CASSANDRA-7719
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7719
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Micha=C3=ABl Figui=C3=A8re
>            Assignee: T Jake Luciani
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> Cassandra newcomers often don't understand that they're expected to use P=
reparedStatements for almost all of their repetitive queries executed in pr=
oduction.
> It doesn't look like Cassandra currently expose any PreparedStatements re=
lated metrics.It would be interesting, and I believe fairly simple, to add =
several of them to make it possible, in development / management / monitori=
ng 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.2#6252)