[DOCS-11343] Add a warning saying that logging with syslog can result in log messages with incorrect timestamps Created: 22/Feb/18  Updated: 29/Oct/23  Resolved: 16/Mar/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Brian Moss
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 5 years, 50 weeks, 5 days ago

 Description   

It has been observed in the field that a syslog daemon is often not able to keep with the rate of logging messages produced by mongod or mongos. I'm going to quote Bruce Lucas here:

The log messages can have an incorrect timestamp because syslog generates the timestamp when it logs the message, not when mongod issues the message, and that can result in log timestamps that are way off - a minute or more in this case. That renders the log file not just useless but seriously misleading as to the timing of events when mongod is under stress.

We should encourage users to use file as the log destination and add a warning about syslog.



 Comments   
Comment by Githook User [ 23/Feb/18 ]

Author:

{'email': 'kallimachos@gmail.com', 'name': 'Brian Moss', 'username': 'kallimachos'}

Message: DOCS-11343 Add warning about incorrect syslog timestamps
Branch: v3.4
https://github.com/mongodb/docs/commit/4c1000b4c8101edc78bfb2b90a7420e92499903f

Comment by Githook User [ 23/Feb/18 ]

Author:

{'email': 'kallimachos@gmail.com', 'name': 'Brian Moss', 'username': 'kallimachos'}

Message: DOCS-11343 Add warning about incorrect syslog timestamps
Branch: master
https://github.com/mongodb/docs/commit/3c59b18ab424117c43a411efe46c7af71f65eee3

Comment by Brian Moss [ 22/Feb/18 ]

PR: https://github.com/mongodb/docs/pull/3238

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