Specify BINLOG MONITOR required for mariadb client setup #1304
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
REPLICA MONITOR is required for SHOW BINLOG STATUS and SHOW BINARY LOGS See https://mariadb.com/kb/en/grant/#binlog-monitor
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue was originally identified here: https://forums.percona.com/t/mariadb-pmm-client-commands-access-denied/32626
Following instructions, I noticed that pmm user was receiving many access denieds.
Looking at my previous mysqld exporter setup, I noticed that the instructions didn't specify to include the BINLOG MONITOR grant for the user.
Once I added BINLOG MONITOR, the number of access denieds dropped.
It also made binlog related graphs start working
BINLOG MONITOR is required for SHOW BINLOG STATUS and SHOW BINARY LOGS
See https://mariadb.com/kb/en/grant/#binlog-monitor