-
Notifications
You must be signed in to change notification settings - Fork 47
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
Feature request (with patch) - Support for Amazon RDS instances #36
Comments
Thanks for sharing. Don't know when I might have time to look at it tough :-/ |
I second this issue. I get plenty of
in my munin-node.log. I did some tests with the mysql console client and it seems that the SQL like Unfortunately the patch from @sfrazer does not apply to my the plugin version i have on Ubuntu 12.04. Any chance that we see this resolved? Or is there another workaround? |
The SUPER permission is not a perl thing, but a MySQL thing. It is needed for the SHOW MASTER LOGS and SHOW SLAVE STATUS queries. You can try to apply the patch below as a workaround.
|
That works, thanks! |
the restriction on replication client may have been relaxed: http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Procedural.Importing.External.Repl.html |
I added the following in munin-monitoring/munin/pull/386 Less privs than super are required for show master status/show slave status. Could be worth adding to mysql.conf 10.0.21-MariaDB-1~jessie-log MariaDB [(none)]> show grants; +--------------------------------------------------------------------------------------------+ | Grants for munin@localhost | +--------------------------------------------------------------------------------------------+ | GRANT PROCESS, REPLICATION CLIENT ON *.* TO 'munin'@'localhost' IDENTIFIED VIA unix_socket | +--------------------------------------------------------------------------------------------+ 1 rows in set (0.00 sec) MariaDB [(none)]> show master status; +--------------------+----------+--------------+------------------+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +--------------------+----------+--------------+------------------+ | mariadb-bin.011145 | 46251284 | | | +--------------------+----------+--------------+------------------+ 1 row in set (0.00 sec) MariaDB [(none)]> show slave status\G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.149.5 Master_User: replica Master_Port: 3306 |
Monitoring Amazon RDS instances with Munin and your plugin poses 2 issues:
I've created a patch for your excellent munin plugin that overcomes both of these limitations. It uses the creation of 2 new environment variables:
mysqlhostname - used ONLY for the config "hostname example.com" output, this doesn't obviate the requirement to put a hostname in the dsn string. This allows whatever node is running this client to present separate nodes to the Munin server. There's probably a better way to do this (one that allows a single workstation to monitor multiple RDS instances) but this was the quickest way to achieve a single RDS instance.
mysqlaws - a yes or no value that defaults to no. If set to yes, the update_master and update_slave subroutines are short-circuited.
Here's the diff against the latest version:
https://gist.github.com/825490
The text was updated successfully, but these errors were encountered: