[SERVER-16847] Diagnostic log output for all query clients should include plan summary string Created: 14/Jan/15 Updated: 06/Dec/22 Resolved: 02/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
It is currently the case that update, delete, findAndModify, group, getMore, aggregate (and possibly more) never generate a plan summary string. If any of these operations generate a line of log output, the log line should include the summary string (though we should come up with something better than runQuery()'s current approach of guessing whether a log line will be generated by checking shouldLog() and elapsedMillis(), which is expensive). |
| Comments |
| Comment by James Wahlin [ 02/May/16 ] |
|
Addressed under |