[SERVER-5278] Progress log messages should include context to identify the process being described Created: 10/Mar/12 Updated: 03/Jan/18 Resolved: 06/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.0.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jared D. Cottrell | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
Various long-running processes such as index building and map/reduce jobs log progress updates like this: 63600/153051 41% If there are no other log messages during the long-running process the resulting log file looks great and is easy to interpret. However, on an active server those messages will be interleaved with various other log messages, making it difficult to figure out what process is being described. It would be useful to get more context for each of the progress log lines so they stand on their own. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 06/Jul/12 ] |
| Comment by Ian Whalen (Inactive) [ 17/May/12 ] |
|
this now has the thread ID included in the 2.1.2 release, but there is still a bit more work to do. |