[CXX-2311] Add server connectionId to command monitoring events Created: 15/Jul/21  Updated: 30/Jun/23

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

Type: Spec Change Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt End to End
has to be finished together with CXX-2638 ConnectionId returned in heartbeats m... Closed
Issue split
Quarter: FY24Q3
Upstream Changes Summary:

DRIVERS-1141:
NA


 Description   

In scope of SERVER-10637, MongoDB 4.2 will return a connectionId in the hello response. This is a number that can be correlated against server log messages, e.g. for this server message:

2018-06-05T13:50:11.978-0400 I NETWORK  [conn2] received client metadata from 127.0.0.1:50254 conn2: { driver: { name: "PyMongo", version: "3.5.1" }, os: { type: "Darwin", name: "Darwin", architecture: "x86_64", version: "10.13.5" }, platform: "CPython 2.7.10.final.0" }

The connectionid reported in the hello response will be 2.

Drivers should sync their command monitoring tests with this commit, update their APM logic to append a new serverConnectionId field to commandStartedEvent, commandSucceededEvent and commandFailedEvent when it is available, and update their test runners to handle UTF schema version 1.6 (featuring the new hasServerConnectionId assertion).

 



 Comments   
Comment by Kevin Albertson [ 26/Apr/23 ]

DRIVERS-2503 changes the specified API of connectionId to be an int64.

Comment by Vinicius Grippa [ 21/Mar/23 ]

Note that the connectionId needs to be supported by int64 or it will overflow.

Generated at Wed Feb 07 22:05:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.