[SERVER-9268] Use existing logging framework to standardize logging in tools Created: 05/Apr/13  Updated: 11/Jun/15  Resolved: 11/Jun/15

Status: Closed
Project: Core Server
Component/s: Logging, Tools
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Shaun Verch Assignee: Michael O'Brien
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-3112 mongo* tools logs should not log to s... Closed
related to SERVER-9282 Audit tools for correct handling of l... Closed
is related to TOOLS-152 Tools should provide way to redirect ... Accepted
is related to SERVER-2011 mongodump, bsondump and mongoexport s... Closed
Participants:

 Description   

The current requirements for logging of tools are:

1. Suppress certain log message (--quiet)
2. Change whether certain messages are going to stdout or stderr to avoid smashing output going to stdout.
3. Multiple different log streams (for fatal errors or just informational messages)
4. Log levels (-vvvv)
5. Redirect log output to file

The only things supported by the current server logging framework are 4 and 5.

The logging framework for the server is currently used in some places in the tools, but only inconsistently since it is not adequate for all cases.

Also note that the tools are tightly integrated with the server, which means that code in the tools can call into server code that uses the existing logging framework. This is a problem because in some cases the tools want to send log messages only to stderr, which isn't supported right now by the existing logging framework used by the server.


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