[DOCS-2747] Document all changes to log file format Created: 19/Feb/14  Updated: 16/Mar/15  Due: 15/Mar/14  Resolved: 05/Sep/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.10

Type: Task Priority: Major - P3
Reporter: Thomas Rueckstiess Assignee: Tim Slavin
Resolution: Done Votes: 0
Labels: sprint-rollover
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-4002 code review for log file changes Closed
Participants:
Days since reply: 9 years, 23 weeks, 5 days ago

 Description   

2.5.x has introduced changes to what is written to the log file, and how.

These changes need to be documented, perhaps in a "Logging" section on the release notes page.

Log file parsing tools will break with the upcoming changes and need to be modified to support the new format, such a list would make the task much easier.



 Comments   
Comment by Kay Kim (Inactive) [ 05/Sep/14 ]

Resolving this one in favor of the linked tracking ticket for next sprint

Comment by Thomas Rueckstiess [ 08/Jul/14 ]

No problem. Let me know when I can have a look at it.

Comment by Tim Slavin [ 08/Jul/14 ]

If it's okay with you, I'll add you to code review later today or first
thing tomorrow morning. I want to add another round of small edits and not
bother you until then.

Tim

On Tue, Jul 8, 2014 at 3:46 PM, Thomas Rueckstiess (JIRA) <jira@mongodb.org>

Comment by Scott Hernandez (Inactive) [ 19/Feb/14 ]

Would also be good to call out the date format (now includes ms+tz-offset) changes for each line

Comment by Thomas Rueckstiess [ 19/Feb/14 ]

I'm mostly concerned about re-occurring structured log messages, like for queries etc, for example changes caused by SERVER-10101 or whatever the outcome is for SERVER-12774.

Generated at Thu Feb 08 07:44:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.