The toString methods of connection pool and server heartbeat event classes (and perhaps others) include a call to ConnectionId#toString, but while ConnectiondId has a ServerId property, it's not included. As a result, if applications log these events by calling toString, they won't see the host names, which makes it kind of useless, e.g. from a recent support case:

 
2022-09-14 02:09:42.402 Received ServerHeartbeatStartedEvent: ServerHeartbeatStartedEvent{connectionId=connectionId{localValue:11, serverValue:173309}} 

We should update either ConnectionId#toString or *Event#toString to include the host name/port and perhaps the cluster id as well.