I have 2 MS 2008R2 Cluster running for MySQL 5.6. I want to monitor both as they are setup as a Windows Service. Well Zabbix works great! It tells me that while the cluster is running MySQL on 1 is on and on 2 is off. Well that is expected, zabbix is correct. At any moment the MySQL service might be shifted from server1 to server 2 and vice versa. So I do want the MySQL service to be monitored. But not always get the service is down on the server that isn't being used. I understand this is how Zabbix works and it is working. What are some Zabbix or non Zabbix solutions to this problem?
To expand the mysql is manual and in stopped mode and when server1 has an issue the cluster takes over, move the SAN storage and starts the MySQL on the next server. Can provide more info or willing to try out of the box. Or maybe I'm just missing a simple idea/step.
Thank you in advanced.
To expand the mysql is manual and in stopped mode and when server1 has an issue the cluster takes over, move the SAN storage and starts the MySQL on the next server. Can provide more info or willing to try out of the box. Or maybe I'm just missing a simple idea/step.
Thank you in advanced.