-
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
MySQL check warning #558
Comments
Did this cause any other issues other than just not being able to get the version number? What do we use the version number for? |
As a result, some metrics were wrong. Some commands changed between <5.0.2 and >5.0.2. We use this version number to know which command to execute. Are concerned: |
Can we determine what version this was introduced in, so we can reliably state 'any users with dd-agent version X--Y using MySQL 5.1.x should use version 3.8.1'? |
It is hard to say because I fixed multiple bugs in the same time, and for sure one of them was here since this check was moved to checks.d (Agent 3.6.2). I didn't check if it also concerns the old MySQL check (i.e. before 3.6.2). Because we probably have other bugs (at least this one: #559), I will probably review the whole check. |
Can we binary-search the versions of the agent by testing them? On Mon, Jul 1, 2013 at 1:50 PM, Benjamin Fernandes <notifications@github.com
|
I'm getting this right now. I have 5.5.31-30.3-log from Percona, and a fresh Datadog Agent installed today (just signed up). |
In the info page:
Happened on MySQL 5.1.x on Red Hat but also Debian Squeeze.
The text was updated successfully, but these errors were encountered: