[SERVER-51847] Make timestamps more readable in Server logs Created: 04/Jan/18  Updated: 27/Oct/23  Resolved: 27/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: sa-groomed, servicearch-product-sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Assigned Teams:
Server Development Platform
Sprint: Evergreen 2018-08-13, Evergreen 2021-02-22
Participants:
Story Points: 2

 Description   

One solution is to consider displaying them as ISO dates, if applicable.

Timestamps currently display like so:

[js_test:apply_ops_wc] 2020-10-26T21:10:32.445+0000 d21522| 2020-10-26T21:10:32.445+00:00 I  INDEX    20345   [ReplWriterWorker-0] "Index build: done building","attr":{"buildUUID":null,"namespace":"applyOps-wc-test.apply_ops_wc","index":"_id_","commitTimestamp":{"$timestamp":{"t":1603746627,"i":10}}}



 Comments   
Comment by Annie Black [ 01/Jun/23 ]

That works for me – thanks for the follow up!

Comment by Alex Neben [ 31/May/23 ]

Jeff and I just synced and we can commit to doing this work but if we just throw it in our backlog it will get lost. While this project is unfinished we can just keep it in our backlog as long as there is a way to refloat this up once the project is done.

annie.black@mongodb.com TLDR my ask is can we keep the ticket in this epic but assigned to SDP backlog? Would that be an ok compromise?

Comment by Annie Black [ 31/May/23 ]

So we mentioned this above but EVG-19385 is meant to enable teams to own this logic themselves, not to have us own team-specific logic. That being said, the work will need to depend on that epic, but if Server would like this custom logic we'll need a Server team to commit to using it.

Comment by Jeffrey Zambory [ 31/May/23 ]

I can't speak for SDP but I think EVG-19385 is likely the best place for this request to be handled in. It looks like it's called out there as well as part of the motivation - can we add this ticket to that epic so that we don't lose track of it and assign this to the EVG backlog?

It feels like Parsley as the log viewing layer is the best place to do this kind of transformation, as that would mean we wouldn't be risking breaking any customer workflows or changing the actual logs we'd be storing for tasks (as would likely have to happen if this was done in Resmoke). 

cc annie.black@mongodb.com 
 
 

Comment by Jason Chan [ 30/May/23 ]

To re-iterate my last comment in case it was missed, since we don't think we want to do this inside the server code, we don't think it belongs to service arch.

Comment by Phoebe Du [ 30/May/23 ]

Hi alexander.neben@mongodb.com jeff.zambory@mongodb.com could you chime in here and see if we can get an agreement of SDP taking this ticket? Service Arch had looked into the issue and didn't think it belongs to us cc jason.chan@mongodb.com iryna.zhuravlova@mongodb.com 

Comment by Iryna Zhuravlova [ 30/May/23 ]

Hey phoebe.du@mongodb.com, was there any discussion around assigning this ticket to SDP? Can we have more context into assigning this to us?

Comment by Annie Black [ 22/May/23 ]

We're reassigning this to Service Arch for now but not sure if this actually belongs with Server Dev Prod if it's a change that's expected to define how all of server's logs look – cc alexander.neben@mongodb.com jeff.zambory@mongodb.com to weigh in.

Comment by Matthew Lewandowski [ 22/May/23 ]

To All: EVG-19385 will allow projects to specify this logic on their own, so evergreen shouldn't own this ticket, but that project will still be a dependency for this ticket.

Comment by Jason Chan [ 16/May/23 ]

Service Arch would like to echo judah.schvimer@mongodb.com's sentiment and prefer to have this change be done as part of Lobster/Parsley or other server log post-processing mechanisms. Assigning this back to the Evergreen team.

Comment by Judah Schvimer [ 30/Oct/20 ]

This was initially an Evergreen ticket to make the change in Lobster.

Comment by Daniel Gottlieb (Inactive) [ 30/Oct/20 ]

judah.schvimer To be clear you're referring to the [BSON]Timestamp commitTimestamp part of the output here? And not the dates/times at the beginning of the log lines.

I'm curious where you were intending the transformation to happen. Lobster? While I find the current output unnecessarily verbose (i.e: I prefer "Timestamp(x, y)"), that's a requirement of the logv2 initiative.

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