Skip to content
This repository has been archived by the owner on May 21, 2019. It is now read-only.

Metric values are not correct in New Relic #24

Open
foobarnum opened this issue May 5, 2014 · 3 comments
Open

Metric values are not correct in New Relic #24

foobarnum opened this issue May 5, 2014 · 3 comments

Comments

@foobarnum
Copy link

We have both datastax opscenter and the 3 legs plugin installed. Were weighing NewRelic as a cassadra monitoring option because it ties in to our alert messaging while this is a paid feature in datastax. Unfortunately the nubers we're getting with the 3legs plugin don't really make sense while the datastax monitoring is largely accurate. Is there tweaking that needs done on our end with the plugin, or is there a bug in the way numbers are gathered and calculated. In the picture below the right pane is datastax and can be taken as a close representation of what is actually going on.

screen shot 2014-05-05 at 10 54 55 am

@jbarbuto
Copy link
Contributor

I believe the read metric discrepancy is at least partially fixed by #29.

@jbarbuto
Copy link
Contributor

Another change that made an even larger improvement is in #31

@magro
Copy link

magro commented Aug 27, 2014

@foobarnum Out of interest, are you using C* 2.x? We're currently evaluating New Relic and I'd also like to have C* monitoring in place. From the README it sounds as if only 1.2.x would be supported,...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants