[SERVER-43807] handle early logging elegantly Created: 03/Oct/19 Updated: 27/Oct/23 Resolved: 27/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gabriel Russell (Inactive) | Assignee: | DO NOT USE - Backlog - Dev Tools |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Developer Tools
|
| Participants: |
| Description |
|
Logging may occur before the logger has been fully configured. This could lead to text-mode messages being sent to the console when what is wanted it json to the console. The console could be a pipe to a json processing program. We need to make a decision about how to deal with potentially mixed format logging. |
| Comments |
| Comment by Sara Williamson [ 10/Dec/19 ] |
|
Very early in process startup, set up the logger to be text mode in stderror until reconfiguration. |