Page History

...

The reason for this implementation is that if FLUSH STATUS is executed with a MySQL server, the server status variables will be are reset to the same value as would be after a server restart. There is one important exception however and that is the 'uptime' status variable itself. This single status variable is not affected by FLUSH STATUS.

So, to get true uptime-based counters in SQL DM for MySQL with servers that do not support the uptime_since_flush_status variable you will need to define a 'base time' in SQL DM for MySQL greater than or equal to the time where FLUSH STATUS was executed last time.

...

Also, note that if the 'base time' is smaller than uptime (or uptime_since_flush_status if available), then 'base time' setting will be is ignored. Using a 'base time' larger than 'uptime' and/or uptime_since_flush_status, then base time would be is considered. If a base time is in future, then most recent collection time would be is considered (similar to Delta).

...

This feature of SQL DM for MySQL saves you time from registering each slave individually. In order to ask SQL DM for MySQL to auto-register all slaves, you would need to 'check' the option to "Auto-Register slaves" in the 'Advanced settings' tab while registering a slave. If in case a master is already registered, click 'Edit Server' and check the 'Auto-Register slaves' in the 'Advanced settings' tab .The MySQL and the SSH details of the slaves are assumed to be the same as that of the 'master'. In case the slave details are different from that of the master, you will have to manually go edit that server and change details.

The auto-registering of slaves is extended to multiple levels of replication. For instance, lets say Server A is a Master that has Server B as the slave. And Server B has Server C as its slave. In such a case, while registering Server A, if you check 'Auto-Register Slaves', then it would register registers A, B and C provided the MySQL and the SSH details of the A is same as that of B.

How does SQL DM for MySQL auto-register all slaves of a given master? SQL DM for MySQL will shoot shoots a "SHOW FULL PROCESSLIST" on the master, and check checks for all the slaves connected. (It will assume the assumes that MySQL and the SSH details of the slaves are the same as that of the master.) To view replication topology click the Replication tab.

Galera

Use this option to Auto register all the Galera nodes of your cluster with SQL DM for MySQL. The MySQL and the SSH details of the nodes are assumed to be the same as that of the node on which you are enabling this option. In case the other node details are different from that of the node on which you are enabling this option, you will have to manually go edit that server and change details. You can do a “Test” to check if SQL DM for MySQL is able to connect to the other nodes. If the “Test” gives a successful message then you can go ahead and click on “Save”. SQL DM for MySQL will then register the detected nodes and you will be redirected to Servers page where you can see all the registered nodes.

...