As an administrator I would like to be able to answer questions like, "why did DS X switch from RS A to RS B?".
We could log more detailed information when a replica (DS) switches from one replication server (RS) to another. However, this can sometimes lead to very noisy replication logs in cases where the network is misbehaving. In addition, users may have switched of logging of this type of event. Instead of or as well as logging, we could publish two pieces of information to the replication monitor: 1) the most recent reason why the DS disconnected from an RS, 2) why the DS is connected to the current RS (e.g. same JVM, same host, same group, etc).