[DRIVERS-1513] Investigate changes in PM-400: Online audit config management Created: 19/Jan/21 Updated: 27/May/22 Resolved: 20/Jan/21 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Not Needed | ||||
| Server Compat: | 5.0 | ||||
| Description |
|
Downstream Change Summary This project will create a new binary, which will need to shipped and documented. Description of Linked TicketEpic Summary SummaryThis project will make all manipulation of audit configuration show up in mongod/s audit logs without requiring a cluster restart. For details, please see product description MotivationAudit configuration is currently present in the mongod/s configuration files. Changing audit configuration requires a restart of cluster nodes and thus takes time to operationalize. The lack of online manipulation of auditing configuration limits how quickly and frequently customers may want to fine-tune audit configuration based on their workloads. It also makes our auditing mechanism feel “legacy” and makes our competition (e.g., Oracle, MySQL) look more appealing for these enterprise-minded customers. It also enables our customers to achieve separation of duties by delegating rights to administer audit configuration to a subset of users. It also allows changes to audit configuration to be reflected in the audit log. Documents |
| Comments |
| Comment by Alexander Golin (Inactive) [ 20/Jan/21 ] |
|
Triage: No work for drivers |