[SERVER-13038] Cleanup verbose query logging (qlog) output Created: 04/Mar/14  Updated: 11/Jul/16  Resolved: 07/Mar/14

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc2

Type: Improvement Priority: Minor - P4
Reporter: David Storch Assignee: David Storch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Cleanup/polish pass on the verbose query logging utility.



 Comments   
Comment by Githook User [ 20/Mar/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-13038 fix indentation in QLOG output

(cherry picked from commit bd89a2c8040b17a7bd2c6d7e94199f26316bbd9b)
Branch: v2.6
https://github.com/mongodb/mongo/commit/c19b54dd42a05208f1da8c8e68bb795c470f2754

Comment by Githook User [ 20/Mar/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-13038 fix indentation in QLOG output
Branch: master
https://github.com/mongodb/mongo/commit/bd89a2c8040b17a7bd2c6d7e94199f26316bbd9b

Comment by Githook User [ 07/Mar/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-13038 verbose query logging cleanup
Branch: master
https://github.com/mongodb/mongo/commit/20a22bdf907a0e2cd60b79f242a7375d84a3ab6a

Comment by David Storch [ 06/Mar/14 ]

The recommendation from the support team is to add the following logging, at log level 2.

If the query is being planned through QueryPlanner::plan:

  • The relevant indices, which are already part of the qlog output.
  • The plan summary string and the score for each plan considered. We can use the same plan summary that appears in the slow query log.
  • The "EOF bonus" line for each plan that hits EOF while picking the best plan.
  • A line giving the plan summary string for the chosen solution.

If the query is being planned through QueryPlanner::planFromCache:

  • A line indicating that the plan was pulled from the cache, plus the plan summary string.
Generated at Thu Feb 08 03:30:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.