Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #332747
Closed
Open
Issue created Jun 06, 2021 by Max Woolf@mwoolf2️⃣Maintainer

[Backend] Emit audit event to HTTP destination

Proposal

Once this issue is complete, namespaces that have set an external destination for their audit logs should see those audit logs being sent to their chosen destination.

Implementation Plan

  • Create a new sidekiq worker to handle sending the audit log.
  • Data about the project or group emitting the event should exist within the JSON payload.
  • When any new audit log is created, the AuditEventService should asynchronously send the data that is written to log/audit_log.json to the desired HTTP endpoint.
Edited Jun 14, 2021 by Max Woolf
Assignee
Assign to
Time tracking