To be future compatible should consider using `type=Table` instead of
`type=ColumnFamily`
depending on your version.
> not matching with the total read requests
the table level metrics for Read/Write latencies will not match the number
of requests you've made. This metric is the amount of time it
okay, let me try it out
On Thu, Aug 31, 2017 at 8:30 PM, Christophe Schmitz <
christo...@instaclustr.com> wrote:
> Hi Jai,
>
> The ReadLatency MBean expose a few metrics, including the count one, which
> is the total read requests you are after.
> See attached screenshot
>
> Cheers,
>
> Christoph
Hi Jai,
The ReadLatency MBean expose a few metrics, including the count one, which
is the total read requests you are after.
See attached screenshot
Cheers,
Christophe
On 1 September 2017 at 09:21, Jai Bheemsen Rao Dhanwada <
jaibheem...@gmail.com> wrote:
> I did look at the document and tried
I did look at the document and tried setting up the metric as following,
does this is not matching with the total read requests. I am using
"ReadLatency_OneMinuteRate"
/org.apache.cassandra.metrics:type=ColumnFamily,keyspace=*,scope=*,name=ReadLatency
On Thu, Aug 31, 2017 at 4:17 PM, Christophe S
Hello Jai,
Did you have a look at the following page:
http://cassandra.apache.org/doc/latest/operating/metrics.html
In your case, you would want the following MBeans:
org.apache.cassandra.metrics:type=Table keyspace= scope=
name=
With MetricName set to ReadLatency and WriteLatency
Cheers,
Chris
Hello All,
I am looking to capture the CF level Read, Write count and Latency. As of
now I am using Telegraf plugin to capture the JMX metrics.
What is the MBeans, scope and metric to look for the CF level metrics?
