-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Description:
If we do document the layout or logging level characters, we now have some new ones (D1-D5), and a small formatting change (I, W, E, F) are now all followed by a blank space.
Engineering Ticket Description:
Currently, there is no quick way to filter log files collected at a higher verbosity to only include lower verbosity messages. By (optionally) including the loglevel in logged message, higher verbosity logs could be quickly filtered to speed initial investigation into issues.
I'm imagining that a call to LOG(3), would include a 3 in the logged message.
Scope of changes
- source/includes/extracts-4.2-changes.yaml
- source/includes/options-mongod.yaml
- source/reference/log-messages.txt
- source/reference/method/db.setLogLevel.txt
- source/reference/parameters.txt
- source/release-notes/4.2-compatibility.txt
- source/release-notes/4.2.txt
- source/includes/options-conf.yaml
- source/reference/configuration-options.txt
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-37743 Include loglevel in log messages
- Closed