[CSHARP-4431] CMAP event logging should include the ConnectionId.LongServerValue Created: 25/Nov/22  Updated: 03/Jan/23

Status: Backlog
Project: C# Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: James Kovacs Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

CMAP event logging currently emits the ConnectionId.LocalValue, which is derived from a local counter and has no relation to the connectionId returned from the server or written in the server logs. ConnectionId.ServerValue stores the connectionId from the server.

In order to allow users to correlate client and server log entries, we must include the ConnectionId.ServerValue in our events and logs. As well CSHARP-4417 introduces ConnectionId.LongServerValue, which is what we should log so as not to accidentally truncate the connectionId returned from the server.


Generated at Wed Feb 07 21:48:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.