[SERVER-46389] Improve replication log line style Created: 25/Feb/20  Updated: 29/Oct/23  Resolved: 17/Mar/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Improvement Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-46771 When using the dual fmtmsg and messag... Closed
Duplicate
is duplicated by SERVER-25495 use local times in repl log messages Closed
Related
is related to SERVER-25495 use local times in repl log messages Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Repl 2020-03-23
Participants:

 Description   

SERVER-46074 and SERVER-46072 improve the attribute names for replication log lines. Additionally, we would like to improve the style of log lines, so that they adhere to the style guide. When adding new format-free versions, we will keep the old version as well, so that it's easy to switch back to text logging, if needed. We will prioritize the most painful or the most common log lines.



 Comments   
Comment by Githook User [ 27/Mar/20 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-46389 Improve replication log line style

(cherry picked from commit 759af0dcb8dd4e13fdcdb8a77907b6dabaf7101e)
Branch: v4.4
https://github.com/mongodb/mongo/commit/0b1bd1ac75787ce46523cab72cedb7715522014e

Comment by Githook User [ 17/Mar/20 ]

Author:

{'name': 'Tess Avitabile', 'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-46389 Improve replication log line style
Branch: master
https://github.com/mongodb/mongo/commit/759af0dcb8dd4e13fdcdb8a77907b6dabaf7101e

Comment by Judah Schvimer [ 05/Mar/20 ]

At Andy's suggestion, we can knock out SERVER-25495 in this pass.

When you convert this message to structured logging, just log the Date_t without any stringification call, and let the logging subsystem handle it.

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