Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-16 Thread Carl Mueller
Your dashboards are great. The only challenge is getting all the data to feed them. On Tue, Oct 16, 2018 at 1:45 PM Carl Mueller wrote: > metadata.csv: that helps a lot, thank you! > > On Fri, Oct 5, 2018 at 5:42 AM Alain RODRIGUEZ wrote: > >> I feel you for most of the troubles you faced,

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-16 Thread Carl Mueller
metadata.csv: that helps a lot, thank you! On Fri, Oct 5, 2018 at 5:42 AM Alain RODRIGUEZ wrote: > I feel you for most of the troubles you faced, I've been facing most of > them too. Again, Datadog support can probably help you with most of those. > You should really consider sharing this

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-05 Thread Alain RODRIGUEZ
I feel you for most of the troubles you faced, I've been facing most of them too. Again, Datadog support can probably help you with most of those. You should really consider sharing this feedback to them. there is re-namespacing of the metric names in lots of cases, and these > don't appear to be

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-04 Thread Carl Mueller
for 2.1.x we had a custom reporter that delivered metrics to datadog's endpoint via https, bypassing the agent-imposed 350. But integrating that required targetting the other shared libs in the cassandra path, so the build is a bit of a pain when we update major versions. We are migrating our

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-02 Thread Alain RODRIGUEZ
Hello Carl, I guess we can use bean_regex to do specific targetted metrics for the > important tables anyway. > Yes, this would work, but 350 is very limited for Cassandra dashboards. We have a LOT of metrics available. Datadog 350 metric limit is a PITA for tables once you get over 10 tables >

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-01 Thread Carl Mueller
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

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-10-01 Thread Alain RODRIGUEZ
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

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-09-28 Thread Carl Mueller
VERY NICE! Thank you very much On Fri, Sep 28, 2018 at 1:32 PM Lyuben Todorov < lyuben.todo...@instaclustr.com> wrote: > Nothing as fancy as a matrix but a list of what JMX term can see. > Link to the online diff here: https://www.diffchecker.com/G9FE9swS > > /lyubent > > On Fri, 28 Sep 2018 at

Re: Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-09-28 Thread Lyuben Todorov
Nothing as fancy as a matrix but a list of what JMX term can see. Link to the online diff here: https://www.diffchecker.com/G9FE9swS /lyubent 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

Metrics matrix: migrate 2.1.x metrics to 2.2.x+

2018-09-28 Thread Carl Mueller
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?