When Replication is stopped or Lagging, there is currently no way to see that in the maxgui. It only says Running with a red X but doesn't show any status about replication on either the dashboard or on the server or monitor pages.
Adding Information to the GUI about Slave Status including if it's in Error, if Slave SQL and Slave IO threads are running, and Seconds behind master at the very least would be helpful. Would like to be able to drill into the red X (or the server that's in a red state) and find the error for why it's red. Maybe even make some information about the error visible on the dash besides the Red text and X.
If I have this dash page on a display screen in an office, I want to be able to look at it and clearly see the problem that
a) that replication is stopped and why (Connectivity error? Duplicate error? Can't find Binlog? etc)
b) that replication is lagging by 300 seconds but still running (and watch that lag increase or decrease to know if I need to intervene or not)