[SERVER-32735] Log process port numbers in passthrough suites Created: 17/Jan/18 Updated: 23/Oct/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | dag, tig-jasper, tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Correctness
|
||||||||
| Participants: | |||||||||
| Description |
|
Passthrough suites log the expected role of the process logging any given message:
But this doesn't include the port number that the process is listening on, which can make it difficult to correlate messages in the logs between processes. I propose adding the port message to the information already logged, so it looks something like:
|
| Comments |
| Comment by Julian Edwards [ 05/Sep/19 ] |
|
This is will now be possible with PM-1116, you can add inject arbitrary information via an arguments map that is part of a buildlogger log's unique id. |
| Comment by Charlie Swanson [ 18/Jan/18 ] |
|
I will not be offended if you don't use it, but I cooked up a patch a little while ago that took a stab at this: better_logging.patch |
| Comment by Max Hirschhorn [ 18/Jan/18 ] |
|
I don't think we should do this ticket without first doing a pass over resmoke.py's log prefixes (i.e. the logging.Logger names) to shorten them. |