I think this isn’t the best place to discuss this. Let me invite you to #mmm on freenode and to our mailing list what you can find here: http://groups.google.com/group/mmm-devel

Thanks for the response and for the tips! I’d need to dig the source a little bit but I’m also wondering what the consequence of running two mmm_mon instances would be on 2 separate servers with identical configurations. Would this cause a conflict with respect to the agents/nodes being monitored or can that be considered as a potential workaround to the mmm_mon failing along with the active master?

Thanks!

you can use heartbeat :)
But monitor is really not a single-point of failure. yes its stand-alone, but MMM agents will keep the last state if something goes wrong. Regarding to the topic, this is another thing what, lets say, I can afford. If the mmmd_mon failed, and the active master failed, something veery nasty thing must happened. And in that case (based on my experiences) our smallest problem was the mysql master’s auto fail-over status :)

But, there is another way, what if mmm_mon and the current active master is on the same uplink and something network outages comes in? Now, this is more like a tip, use different network and power supply for each of your mysql master and mmm_mon :)