Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
None
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.