Investigate changes in PM-400: Online audit config management

    • Type: Epic
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Downstream Change Summary

      This project will create a new binary, which will need to shipped and documented.

      Description of Linked Ticket

      Epic Summary

      Summary

      This 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

      Motivation

      Audit 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

      Product Description
      Scope document
      Technical Design

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None
              None
              None