-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics, Logging, Querying
-
None
-
Query
-
Minor Change
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).
- duplicates
-
SERVER-23259 Report planSummary in per-operation diagnostic log message and profiler for all relevant ops/commands
- Closed
- is duplicated by
-
SERVER-16931 Always print planSummary if a query was involved
- Closed
-
SERVER-19715 Aggregation Loglines do not print the query plan
- Closed
- is related to
-
SERVER-16265 Add query details to getmore entry in profiler and db.currentOp()
- Closed
- related to
-
SERVER-17862 Unify stats reporting for log/profiler across CRUD operations
- Closed