[DOCS-11312] v3.4: Audit and log rotation not always simultaneous Created: 12/Feb/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Francisco Alanis | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/v3.4/tutorial/configure-auditing/index.html |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
The documentation for audit configuration here mentions: "The audit file rotates at the same time as the server log file." However, it doesn't seem this is always the case. For example, on restart by default the system log will be "rotated" (or backed up) while the audit file will stay the same. I suggest something more specific like "Log rotation via a SIGUSR1 signal or a logRotate command affects the audit file as well as the server log file" or something along those lines. This is to avoid confusion as users/customers might expect audit file to be rotated too on startup when logAppend is false. Thanks. |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |