[SERVER-15520] Logging with --syslog results in less accuracy due to lack of mongodb timestamp Created: 03/Oct/14 Updated: 19/May/15 Resolved: 15/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James O'Leary | Assignee: | Matt Kangas |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
*nix |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | run mongod --syslog |
||||||||
| Participants: | |||||||||
| Description |
|
MongoDb 2.6.0 - 2.6.4 logging seems to have removed the timestamp from the syslog message. As a result the default syslog using RFC3339 loses granularity on time stamps : MongoDB 2.4.10
MongoDB 2.6.0
|
| Comments |
| Comment by Matt Kangas [ 15/Jan/15 ] |
|
When logging with --syslog, the timestamp is created by the syslog daemon. mongod cannot configure it. We are not going to add an separate timestamp generated by mongod to syslog output. |