CMAP event logging should include the ConnectionId.LongServerValue

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            James Kovacs
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: