[SERVER-4321] MongoDB Logging Related Issue Created: 18/Nov/11  Updated: 15/Aug/12  Resolved: 10/Aug/12

Status: Closed
Project: Core Server
Component/s: Logging, Security
Affects Version/s: 1.9.0
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Saurabh Dave Assignee: Mark porter
Resolution: Duplicate Votes: 8
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows/Linux/Freebsd


Issue Links:
Depends
depends on SERVER-1891 Audit "DDL" operations Closed
depends on SERVER-6407 Authenticate users via LDAP proxy Closed
depends on SERVER-2957 Add ability to log to syslog Closed
depends on SERVER-3591 Kerberos Support Closed
Participants:

 Description   

1. Separate system logs from audit logs
2. Add controls to permit logging granularity levels, both for system logs and audit logs
3. Add controls to permit log rollover based on both file size and duration.
4. Support for remote log file storage.
5. Ensure that user credentials (including hash values) are not written to log files



 Comments   
Comment by Mark porter [ 10/Aug/12 ]

Duplicate of existing tickets and linked accordingly.

Comment by Mark porter [ 07/Aug/12 ]

Hi Saurabh,

1. SERVER-1891 takes care of this.

2. This sounds like the switch [debug, informational etc) in syslog to control the verbosity of the debugging level. Verbosity can be controlled today in the following ways:

  • at runtime, either through the command-line arguments or the configuration file as outlined here

3. Log rotation is an existing feature. It can be done via the shell (easily incorporated into a cron job) or a SIGUSR1 signal. SERVER-1891 covers a separate audit log file.

4. SERVER-2957 covers this.

5. New authentication schema will resolve this, please see SERVER-3591 & SERVER-6407.

Thanks

Mark

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