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

Alert MySQL Last IO/SQL Errors when replication enabled #640

Closed
wants to merge 3 commits into from

Conversation

brettlangdon
Copy link
Member

This will send events when the MySQL slave receives a Last_IO_Error or Last_SQL_Error. It also tracks whether an error has occurred or not so it doesn't send events every time this check runs, just when the "status" changes (e.g. there is an error to there are no more errors).

The reasoning behind this is we have found with our MySQL slaves that sometimes they stop replicating when there is a IO or SQL error when replicating and we want a way to receive notifications when this happens.

@dcrosta
Copy link
Contributor

dcrosta commented Sep 12, 2013

Hey @DataDog can we get any movement on this? It would be very useful for us.

@remh
Copy link
Contributor

remh commented Sep 12, 2013

Hi Brett, Dan.
Thanks for this!

We are currently working on service checks that would be a more general solution for that kind of checks so we are not going to merge that in.

Maybe you could make a custom checks.d out of it so you won't be expecting the release of service checks ?

Thanks again for that and sorry for not merging that in.

@remh remh closed this Sep 12, 2013
@ghost
Copy link

ghost commented Oct 14, 2013

Hey, any update about this functionality? We have also run into situations where we'd very much like to be notified upon error (this can happen due to timeout or some other exceptional circumstance). Simply notifying based on lag replication seems insufficient as the replication error is even more significant in certain cases.

Thanks

@ghost
Copy link

ghost commented Oct 14, 2013

Sorry, just saw this: #671

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

Successfully merging this pull request may close these issues.

3 participants