[SERVER-77190] Include the whole client metadata in telemetry key, not just appName Created: 16/May/23 Updated: 07/Feb/24 Resolved: 31/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Maddie Zechar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | QO 2023-05-29 | ||||||||||||
| Participants: | |||||||||||||
| 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:
Note many fields there are optional: https://github.com/10gen/mongo/blob/253d4ea05ac72c44294293ed8e9b28f473c93862/src/mongo/rpc/metadata/client_metadata.h#L64 |
| Comments |
| Comment by Githook User [ 07/Feb/24 ] |
|
Author: {'name': 'Erin Zhu', 'email': 'erin.zhu@mongodb.com', 'username': 'erinzhu001'}Message: Includes backports of the following |
| Comment by Githook User [ 31/May/23 ] |
|
Author: {'name': 'Maddie Zechar', 'email': 'maddie.zechar@mongodb.com', 'username': 'madelinezec'}Message: |