When a SignalR connection gets replaced, we see the same Id in the log twice
gingters opened this issue · 0 comments
When a SignalR connection is re-established, the connection id might change.
We try to log this, but then we have an entry like that:
Dropped connection Rvj40OgbjI6kEPnSZDjRBw in favor of new connection Rvj40OgbjI6kEPnSZDjRBw
Both entries are the new connection id.
The problem is that we use the same place holder {ConnectionId} for both parts.
Solution: We need to use different place holders here (ConnectionId and NewConnectionId), so that when we search for log entries with a specific ConnectionId = value, the log will tell us the switch of the ConnectionId to the NewConnectionId in the last entry and we can search for the new one afterwards. Otherwise the log would just stop and we don't have the switch in correlation to the old id.