Description:
We currently have several dev mysqld instances running on one server.
They are currently configured each to be bound to a specific ip address
# netstat -an | grep 3306 | grep LISTEN
tcp 0 0 10.149.204.14:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.21:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.22:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.20:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.18:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.15:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.19:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.23:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.17:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.26:3306 0.0.0.0:* LISTEN
tcp 0 0 10.149.204.16:3306 0.0.0.0:* LISTEN
We want to enable the proxy for each instance so the developers can monitor the queries they are doing.
So we would expect the proxy to be listening/bound to the same ip address:4040 and then forward connections to the corresponding :3306 addressed mysqld.
I could imagine doing this by adjusting the etc/instances/XXXXX/agent-instance.ini file and adding a section:
[mysql-proxy]
proxy-address=XXXXXX:4040
proxy-backend-addresses = XXXXXX:3306
and to use the "global values" in etc/mysql-monitor-agent.ini if the values are missing here.
Currently using multiple proxies requires configuring an agent per "proxy instance" and this is quite tedious. Having one single agent capable of proxying and forwarding to the right mysqld would be more convenient.
Installing/Upgrading and maintaining a single agent is also much simpler.
How to repeat:
N/A
Suggested fix:
See description
