Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-5141

Make audit event logging more flexible

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      Bitbucket Server Audit Logging only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on specific events but can't afford the performance impact of setting audit logging to LOW and enabling auditing of every event.

      Suggested Solution

      Specify certain events that are enabled for auditing with rest endpoints or a bitbucket property.

      Workaround

      None

          Form Name

            [BSERV-5141] Make audit event logging more flexible

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3394334 ] New: JAC Suggestion Workflow 3 [ 3620989 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2685813 ] New: JAC Suggestion Workflow [ 3394334 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 722221 ] New: BSERV Suggestions Workflow [ 2685813 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ben Stuart (Inactive) made changes -
            Link New: This issue was cloned as BSERV-10796 [ BSERV-10796 ]
            Ben Stuart (Inactive) made changes -
            Link Original: This issue is duplicated by BSERV-10696 [ BSERV-10696 ]
            Ben Stuart (Inactive) made changes -
            Description Original: h3. Problem Definition

            [Bitbucket Server Audit Logging|https://docs.atlassian.com/bitbucket-server/rest/4.7.1/bitbucket-audit-rest.html#idp9552] only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on certain events but can't afford the performance impact of having everything enabled.

            h3. Suggested Solution

            Specify certain events that are enabled for auditing with rest endpoints or a bitbucket property.

            h3. Workaround
            None
            		New: h3. Problem Definition

            [Bitbucket Server Audit Logging|https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html#BitbucketServerconfigproperties-Audit] only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on specific events but can't afford the performance impact of setting audit logging to LOW and enabling auditing of every event.

            h3. Suggested Solution

            Specify certain events that are enabled for auditing with rest endpoints or a bitbucket property.

            h3. Workaround
            None
            Ben Stuart (Inactive) made changes -
            Description Original: As a Stash admin, it would be good to be able to overwrite the Audit events priorities as different customers believe that some events should have different priorities to what is currently shipped with Stash and documented on:
            - [Audit events in Stash|https://confluence.atlassian.com/display/STASH/Audit+events+in+Stash]

            h3. Problem Definition

            [Bitbucket Server Audit Logging|https://docs.atlassian.com/bitbucket-server/rest/4.7.1/bitbucket-audit-rest.html#idp9552] only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on certain events but can't afford the performance impact of having everything enabled.

            h3. Suggested Solution

            Specify certain events following the endpoints:
            * {noformat}http://example.com/rest/audit/1.0/projects/\{projectKey}/events [GET]{noformat}
            * {noformat}http://example.com/rest/audit/1.0/projects/\{projectKey}/repos/{repositorySlug}/events [GET]{noformat}

            h3. Workaround
            None
            		New: h3. Problem Definition

            [Bitbucket Server Audit Logging|https://docs.atlassian.com/bitbucket-server/rest/4.7.1/bitbucket-audit-rest.html#idp9552] only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on certain events but can't afford the performance impact of having everything enabled.

            h3. Suggested Solution

            Specify certain events that are enabled for auditing with rest endpoints or a bitbucket property.

            h3. Workaround
            None
            Ben Stuart (Inactive) made changes -
            Summary Original: Make event priorities flexible New: Make audit event logging more flexible
            Ben Stuart (Inactive) made changes -
            Description Original: As a Stash admin, it would be good to be able to overwrite the Audit events priorities as different customers believe that some events should have different priorities to what is currently shipped with Stash and documented on:
            - [Audit events in Stash|https://confluence.atlassian.com/display/STASH/Audit+events+in+Stash]             		New: As a Stash admin, it would be good to be able to overwrite the Audit events priorities as different customers believe that some events should have different priorities to what is currently shipped with Stash and documented on:
            - [Audit events in Stash|https://confluence.atlassian.com/display/STASH/Audit+events+in+Stash]

            h3. Problem Definition

            [Bitbucket Server Audit Logging|https://docs.atlassian.com/bitbucket-server/rest/4.7.1/bitbucket-audit-rest.html#idp9552] only allows you to enable audit logging in batches. Enterprise customers sometimes need strict auditing on certain events but can't afford the performance impact of having everything enabled.

            h3. Suggested Solution

            Specify certain events following the endpoints:
            * {noformat}http://example.com/rest/audit/1.0/projects/\{projectKey}/events [GET]{noformat}
            * {noformat}http://example.com/rest/audit/1.0/projects/\{projectKey}/repos/{repositorySlug}/events [GET]{noformat}

            h3. Workaround
            None
            Ben Stuart (Inactive) made changes -
            Link New: This issue is duplicated by BSERV-10696 [ BSERV-10696 ]

              Unassigned Unassigned
              tbomfim ThiagoBomfim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: