[SERVER-50945] Allow for local logging with jasper in resmoke Created: 15/Sep/20  Updated: 27/Oct/23  Resolved: 03/Apr/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Backlog - Evergreen Team (Inactive)
Resolution: Gone away Votes: 0
Labels: evg-plt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Evergreen
Participants:

 Description   

Currently, local logging is done by propagating information to the top of the logger hierarchy where it's dealt with by either a file handler or a stream handler (for file logging and stdout logging, respectively).



 Comments   
Comment by Brooke Miller [ 03/Apr/23 ]

Closing as Gone Away since PM-2695 is complete.

Comment by April Schoffer [ 18/Apr/22 ]

This would only be necessary if we move mongo* projects to use resmoke, which is currently no longer planned. This will likely be closed as gone away when PM-2695 is complete.

Comment by April Schoffer [ 08/Oct/20 ]

We're removing this from the Use Jasper in Resmoke project (PM-1439). Currently jasper is logging to stdout, we can handle updates to resmoke logging to the 3 separate files separately.

Comment by Julian Edwards [ 21/Sep/20 ]

We need to figure out which logger is passed to the jasper server process. The server is started via a python process and currently we pass in the resmoke logger, which has the "resmoke" prefix. This results in a double prefix of the logs.

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