[SERVER-85138] guide for log messages and debug levels Created: 29/Jul/14 Updated: 12/Jan/24 Resolved: 19/Aug/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | 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: |
|
||||||||||||||||||||||||||||
| Sprint: | Server 2.7.5, Server 2.7.6 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
Provide guidelines on log message style and assigning appropriate debug log levels (LOG() macro). Debug Logging Enhancements: Logging Module Spec (March 2013): Outline: Top of file (before platform/basic.h) Always include mongo/util/log.h where logging is done. No more logging in headers
severe(), error(), warning(), log() and LOG() will use log component defined in MONGO_LOG_COMPONENT_DEFAULT is available. Otherwise defaults to LogComponent::kDefault. severe(), error(), warning(), log() will accept optional log component argument if MONGO_LOG_COMPONENT is not appropriate for the current scope. For configuration, see mongo db manual for logComponentVerbosity server parameter or systemLog.component YAML configuration option. |
| Comments |
| Comment by Benety Goh [ 19/Aug/14 ] |
|
Changes have been made to:
|