[SERVER-14415] log component hierarchy Created: 01/Jul/14  Updated: 03/Sep/16  Resolved: 16/Jul/14

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.7.2
Fix Version/s: 2.7.4

Type: New Feature Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: community-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-5092 Better named logging with tracing Closed
Related
related to SERVER-85138 guide for log messages and debug levels Closed
is related to DOCS-3694 Document named logging Closed
Tested
Sprint: Server 2.7.4
Participants:
Linked BF Score: 0

 Description   

Currently log components (introduced in SERVER-5092) are laid out in a flat namespace with a default:

  • Debug
    • Access Control
    • Commands
    • Indexing
    • Networking
    • Query
    • Replication
    • Sharding
      **Storage

It would be desirable to support a hierarchy of log components:

  • Default
    • Access Control
    • ...
    • Storage
      • Journalling

In the example above, if the log level for Default is 2 and Storage is set to 3 and Journalling is not configured, Journalling would inherit Storage's log level so that MONGO_LOG(3, Journalling) messages would be written to the log destination.



 Comments   
Comment by Githook User [ 16/Jul/14 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-14415 added yaml config options to set log component hierarchy verbosity levels
Branch: master
https://github.com/mongodb/mongo/commit/6f8e975b7a7ef18baf25281b206288a74deb5972

Comment by Githook User [ 16/Jul/14 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-14415 extended LogComponent and LogComponentSettings to support hierarchy of component log levels
Branch: master
https://github.com/mongodb/mongo/commit/758d86f85a26578a5c99c2f1f128bbe86752bb32

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