[SERVER-29115] Keep track of how many times a particular query shape was used and its cumulative latency Created: 08/May/17 Updated: 20/Dec/23 Resolved: 20/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Backlog - Query Integration |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Integration
|
||||||||
| Participants: | |||||||||
| Description |
|
For index building purposes it would be extremely useful to have a counter per query shape and the associated cumulative latency, even if it's not super accurate. While it's possible to parse profiler and/or mongod logs to obtain the same information, this generates extra disk IO and requires users to essentially duplicate the effort (since we have to determine the shape and measure the latency in the server anyway). |
| Comments |
| Comment by Charlie Swanson [ 20/Dec/23 ] |
|
PM-3120 is the project tracking the backport. INIT-377 tracks other projects to extend the metrics collected here and also to extend the tracking to write commands. |
| Comment by Charlie Swanson [ 20/Dec/23 ] |
|
This issue was implemented via a whole project, fully released in 7.3. There are plans to backport this to earlier versions. You can watch |