[SERVER-43809] Refactor LogManager and how it is configured Created: 03/Oct/19 Updated: 29/Oct/23 Resolved: 15/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Dev Tools 2019-10-21 |
| Participants: |
| Description |
|
Currently the LogManager have a bunch of functions to setup, attach and detach logging backends. These functions refer to the global log domain implicitly. They also give the impression that the log manager can be re-configured multiple times. This should all be cleaned up to make the interface consistent with how it is used. |
| Comments |
| Comment by Githook User [ 15/Oct/19 ] |
|
Author: {'name': 'Henrik Edin', 'username': 'henrikedin', 'email': 'henrik.edin@mongodb.com'}Message: Configuration via a single method to make it clearer on how to use |