You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 21, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
@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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: