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

Metrics collection for Cassandra Datastax doesn't recover after Cassandra restart #1118

Closed
garnermccloud opened this issue Sep 15, 2014 · 5 comments
Milestone

Comments

@garnermccloud
Copy link
Contributor

From Org 4456 (https://datadog.desk.com/agent/case/14498):

"I wanted to submit a bug related to the cassandra datastax agent config. It doesn't appear to recover automatically to a cassandra restart. You have to restart the agent in order to start collecting metrics again."

@garnermccloud
Copy link
Contributor Author

Similar bug report filed in this case too for Postgres: https://datadog.desk.com/agent/case/14670

Only Agent restart starts collection of Postgres metrics even if Postgres has already been restarted.

@remh remh closed this as completed Sep 17, 2014
@remh remh reopened this Sep 17, 2014
@remh
Copy link

remh commented Sep 17, 2014

For the cassandra one can you ask what version of the agent they are using and the log files (as usually)? It should start collecting metrics without having to bounce the agent.

For postgres it's a different know issue #1003 and will be fixed with the next version of the agent.

@remh
Copy link

remh commented Sep 26, 2014

@garnermccloud any input on the cassandra issue related to my question ? If not i'll close the issue.

@remh remh added this to the 5.1.0 milestone Sep 26, 2014
@garnermccloud
Copy link
Contributor Author

Waiting on response from user

@garnermccloud
Copy link
Contributor Author

User responded: "haven’t had a false positive since 3 days ago (it magically stopped happening). I’m keeping an eye out on things and if it happens again then I’ll forward over the information."

So I'll close this out and reopen if he has an issue.

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

2 participants