Skip to content
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

Closed
jedrzejsieracki opened this issue Sep 15, 2015 · 9 comments
Closed

[cassandra] add configuration support for Cassandra 2.2+ #1916

jedrzejsieracki opened this issue Sep 15, 2015 · 9 comments
Assignees
Milestone

Comments

@jedrzejsieracki
Copy link

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.

@yannmh
Copy link
Member

yannmh commented Sep 16, 2015

Thanks for reporting the issue @jedrzejsieracki !

Starting from Cassandra 2.2+, beans are exposed under the new org.apache.cassandra.metrics.ColumnFamily naming convention (rather than the org.apache.cassandra.db.ColumnFamilies one). As you highlighted, it means that the beans defined in the default cassandra.yaml file are not matched, thus fetched via JMXFetch.

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.

@yannmh yannmh self-assigned this Sep 16, 2015
@yannmh yannmh added this to the 5.6.0 milestone Sep 16, 2015
@jippi
Copy link
Contributor

jippi commented Sep 18, 2015

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 ?

@yannmh
Copy link
Member

yannmh commented Sep 18, 2015

@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.

@jippi
Copy link
Contributor

jippi commented Oct 31, 2015

@yannmh been a few months, and still not fixed? :(

Why not make the configuration public so everyone can benefit and try it out

@irabinovitch
Copy link
Contributor

@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,
Ilan
Dir, Technical Community
Datadog

@gtmtech
Copy link

gtmtech commented Nov 18, 2015

Hi, whats the status on this? This is holding us up too. thanks!

@yannmh
Copy link
Member

yannmh commented Nov 18, 2015

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 cassandra.yaml.example YAML configuration file to actually fetch the new relevant MBeans. Since there is no direct mapping between the 'old' and the 'new' MBeans, we are progressively putting the list together. As an aside, any feedback is also much appreciated 😄

In the meantime, please feel free to use this temporary YAML file as a workaround.
https://gist.github.com/yannmh/c1a4a85d5cab69be39da

@remh remh modified the milestones: 5.6.3, 5.6.0 Nov 19, 2015
@olivielpeau olivielpeau modified the milestones: 5.7.0, 5.6.3 Dec 4, 2015
@olivielpeau
Copy link
Member

The default yaml file has been made compatible with Cassandra 2.2+ by #2142, which will be released with the 5.7.0 agent.

@olivielpeau
Copy link
Member

Closing this issue as the PR that fixes it (see comment above) is merged into master.

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

No branches or pull requests

7 participants