[SERVER-73405] Collect telemetry on shard servers for find and agg Created: 27/Jan/23 Updated: 29/Oct/23 Resolved: 08/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joshua Lapacik (Inactive) | Assignee: | Ted Tuckman |
| 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-02-06, QO 2023-02-20 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
A new optional field will need to be added to the find and aggregate commands for transmitting the telemetry key (HostAndPort + md5 hash) to mongod. We should update the telemetry store on mongod in the following ways:
When mongos receives a command request, it will generate a hash(md5) from the telemetry key, creating a shape ID (HostAndPort of mongos + md5 hash), adding it to the requests sent to mongod, and accumulating the above metrics in the telemetry store at the end of execution. Note, we should disallow external $telemetry calls (ones not originating from mongos) on shard servers. |
| Comments |
| Comment by Githook User [ 09/Feb/23 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Githook User [ 08/Feb/23 ] |
|
Author: {'name': 'Ted Tuckman', 'email': 'ted.tuckman@mongodb.com', 'username': 'TedTuckman'}Message: |