Cassandra metrics change starting with version 1.2 about jmxfetch HOT 5 CLOSED

We stay with the old style of metrics, until 2.x has become the mature version. Then we can decide what to do.

from jmxfetch.

I investigated this and it's going to require some changes to the way we collect tags from Cassandra. Here's an example bean:

Bean name: org.apache.cassandra.metrics:type=ColumnFamily,keyspace=Intake,scope=api_log,name=PendingTasks - Attribute name: Value - Attribute type: java.lang.Object

The metric that we'd want from this would be along the lines of: cassandra.pending_tasks with tags: keyspace:intake, columnfamily:api_log

But jmxfetch turns this into: cassandra.metrics.value with tags: name:pendingtasks keyspace:intake type:columnfamily scope:api_log

As a result we'd have to add some function for Cassandra metrics (or make the jmx config extensible) to allow the jmx parser to create metric names like cassandra.$name and tags like $type:$scope.

We also wouldn't have good mechanisms for filtering the metrics that are collected, as we can't filter by the name attribute.

The deprecated metrics are going to be dropped in Cassandra 3.0.

from jmxfetch.

could probably be just a new version of https://github.com/DataDog/jmxfetch/blob/master/src/main/java/org/datadog/jmxfetch/reporter/Reporter.java#L105-L107

from jmxfetch.

any update on this? Currently the cassandra jmx is more or less broken :(

from jmxfetch.

Fixed with #79, closing.

from jmxfetch.