[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:
Duplicate
duplicates SERVER-23259 Report planSummary in per-operation d... Closed
is duplicated by SERVER-16931 Always print planSummary if a query w... Closed
is duplicated by SERVER-19715 Aggregation Loglines do not print the... Closed
Related
related to SERVER-17862 Unify stats reporting for log/profile... Closed
is related to SERVER-16265 Add query details to getmore entry in... Closed
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 SERVER-23259.

Generated at Thu Feb 08 03:42:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.