-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cassandra] add configuration support for Cassandra 2.2+ #1916
Comments
Thanks for reporting the issue @jedrzejsieracki ! Starting from Cassandra 2.2+, beans are exposed under the new We are working on fix for Datadog agent 5.6.0, i.e. updating the YAML configuration file and improving JMXFetch 'default' support for these metrics (more information). In the meantime, feel free to contact our support team: we;ll be happy to provide you a short term solution with an updated configuration tu monitor your Cassandra 2.2+ instances. |
I'm hitting the same problem using cassandra 2.2 and almost no data is collected Can you share an intermediate configuration file that is compatible ? |
@jippi would you mind contacting our support team please ? They can provide a short term solution with an updated configuration tu monitor your Cassandra 2.2+ instances. |
@yannmh been a few months, and still not fixed? :( Why not make the configuration public so everyone can benefit and try it out |
@jippi Apologies for the delays here. I will follow up with our team internally to see where we stand on this one. Feel free to mention me on any issues/PRs or reach out via email anytime. Regards, |
Hi, whats the status on this? This is holding us up too. thanks! |
Hi @gtmtech, My apologies for the late response. Datadog Agent 5.6.0 changes includes improvements to support Cassandra 2.2+ MBeans. Please see CHANGELOG, #50 and #79. To sum up, the Datadog Agent is now able to pull metrics using the new naming convention and submit them with a suitable metric name. The next step we are working on, is now updating In the meantime, please feel free to use this temporary YAML file as a workaround. |
The default yaml file has been made compatible with Cassandra 2.2+ by #2142, which will be released with the 5.7.0 agent. |
Closing this issue as the PR that fixes it (see comment above) is merged into master. |
There are JMX attributes names changes since Cassandra 2.2 and default cassandra.yaml only matches nine of them.
From what I see, the per table WriteCount metrics are gone, so not sure how to proceed with extracting total WriteCount for the cluster - good luck.
The text was updated successfully, but these errors were encountered: