That's great too, thank you.

Datadog 350 metric limit is a PITA for tables once you get over 10 tables, but I guess we can use bean_regex to do specific targetted metrics for the important tables anyway.

On Mon, Oct 1, 2018 at 4:21 AM Alain RODRIGUEZ <> wrote:
Hello Carl,

Here is a message I sent to my team a few months ago. I hope this will be helpful to you and more people around :). It might not be exhaustive and we were moving from C*2.1 to C*3+ in this case, thus skipping C*2.2, but C*2.2 is similar to C*3.0 if I remember correctly in terms of metrics. Here it is for what it's worth:

Quite a few things changed between metric reporter in C* 2.1 and C*3.0.
- ColumnFamily --> Table
- XXpercentile --> pXX
- 1MinuteRate -->  m1_rate
- metric name before KS and Table names and some other changes of this kind.
- ^ aggregations / aliases indexes changed because of this (using graphite for example) ^
- ‘.value’ is not appended in the metric name anymore for gauges, nothing instead.

For example (graphite):

aliasByNode(averageSeriesWithWildcards(cassandra.$env.$dc.$$ks.$table.ReadLatency.95percentile, 2, 3), 1, 7, 8, 9)

aliasByNode(averageSeriesWithWildcards(cassandra.$env.$dc.$$ks.$table.p95, 2, 3), 1, 8, 9, 10)

Alain Rodriguez - @arodream -
France / Spain

The Last Pickle - Apache Cassandra Consulting

Le ven. 28 sept. 2018 à 20:38, Carl Mueller <> a écrit :
VERY NICE! Thank you very much

On Fri, Sep 28, 2018 at 1:32 PM Lyuben Todorov <> wrote:
Nothing as fancy as a matrix but a list of what JMX term can see. 
Link to the online diff here:


On Fri, 28 Sep 2018 at 19:04, Carl Mueller <> wrote:
It's my understanding that metrics got heavily re-namespaced in JMX for 2.2 from 2.1

Did anyone ever make a migration matrix/guide for conversion of old metrics to new metrics?