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

Enable different backend monitoring configuration per hostgroup. #4790

Open
rialg opened this issue Jan 17, 2025 · 0 comments
Open

Enable different backend monitoring configuration per hostgroup. #4790

rialg opened this issue Jan 17, 2025 · 0 comments

Comments

@rialg
Copy link

rialg commented Jan 17, 2025

The mysql backend monitoring relies on sharing the same global variables for setting up hostgroup monitoring. This has the immediate effect that all backends must share the same monitoring user (monitor_username and monitor_password) , thus if this credentials don't exist in the mysql server, the heartbeats/ping will fails and potentially already working connections from other valid mysql_users will be killed by the hostgroup manager.

Incidentally, I am experiencing this issue when sharing the same config between unix socket connections that are authenticated using username:password credentials and IAM authenticated connections to mysql. Although an immediate workaround is to have two proxysql services running with different configs, it would make more sense for my set up to have all the hostgroups configured using the same instance.

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

No branches or pull requests

1 participant