[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: Text File better_logging.patch    
Issue Links:
Related
related to SERVER-50085 Make it easier to correlate mongo pro... Closed
Assigned Teams:
Correctness
Participants:

 Description   

Passthrough suites log the expected role of the process logging any given message:

[ShardedClusterFixture:job11:configsvr:primary]

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:

[ShardedClusterFixture:job11:configsvr:primary:20010]



 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. I made some pretty controversial decisions about the shortened names, but I did condense them, and I think that patch allows custom loggers that will include the port as part of the fixture name.

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.

Generated at Thu Feb 08 04:31:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.