PCT-985 InnoDB Stats are not re-enabled after MySQL restart

This seems wrong to me. Connecting and connection state != restart because restart monitoring is not responsible for/aware of connecting/connection state, it simply tells the listener/subscriber "whatever's at the end of the DSN you registered was restarted". Sometimes that also means the connection was lost, but not always. For example, with QAN, we can be not connected (between intervals), but get a restart notice. In this case, we re-config the MySQL slow log and there's no further implications for connections.