Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Query Optimization
-
Fully Compatible
-
QO 2023-05-29
Description
After discussing the troubles of many internal connections/operations being recorded, we think that tracking the entire client metadata including the driver name and version will be helpful in filtering out the noise.
That would be this thing in the code, and would cause this kind of diff in the output of $queryStats:
{
|
cmdNs: {db: "test", coll: "example_coll"},
|
command: "find"
|
filter: {a: {$gt: "?number"}},
|
sort: {a: -1},
|
- applicationName: "example",
|
+ client: {
|
+ application: {name: "example"},
|
+ driver: {name: "string", version: "string"},
|
+ os: {type: "string", name: "string", architecture: "string", version: "string"},
|
+ mongos: {host: "string", client: "string", version: "string"},
|
+ }
|
}
|
Note many fields there are optional: https://github.com/10gen/mongo/blob/253d4ea05ac72c44294293ed8e9b28f473c93862/src/mongo/rpc/metadata/client_metadata.h#L64
Attachments
Issue Links
- is depended on by
-
SERVER-85099 Tracking: Milestone 1
-
- Closed
-
-
SERVER-85105 Tracking: PM-2885 Milestone 0
-
- Closed
-