π React to this issue if you need this feature β helps us prioritise.
Problem
GitLab Audit Events expose who did what, when β instance/group/project scoped. Premium+ feature, useful for compliance investigations. We don't expose any audit-events tool.
Investigation done (current state)
Verified against src/entities/:
- β
grep -ri 'audit.*event' src/ returns 0 hits
Re-verify before coding:
grep -rIni 'audit' src/entities/
ls src/entities/ | grep audit
Acceptance criteria
- New entity
src/entities/audit_events/ with read-only browse_audit_events actions:
list_instance (admin-only, GET /audit_events)
list_group (Premium+, group owner/admin)
list_project (Premium+, project owner/admin)
get (single audit event)
- Tier-gated: Premium+ for group/project, Ultimate for some advanced filters
- No write actions (audit events are immutable by design)
- Integration test gated via
describeIfTier('premium', ...)
GitLab API
Estimate
1d
Context
Found during GitLab 18β19 API landscape analysis.
π React to this issue if you need this feature β helps us prioritise.
Problem
GitLab Audit Events expose who did what, when β instance/group/project scoped. Premium+ feature, useful for compliance investigations. We don't expose any audit-events tool.
Investigation done (current state)
Verified against
src/entities/:grep -ri 'audit.*event' src/returns 0 hitsRe-verify before coding:
Acceptance criteria
src/entities/audit_events/with read-onlybrowse_audit_eventsactions:list_instance(admin-only,GET /audit_events)list_group(Premium+, group owner/admin)list_project(Premium+, project owner/admin)get(single audit event)describeIfTier('premium', ...)GitLab API
/audit_events(instance),/groups/:id/audit_events,/projects/:id/audit_eventsEstimate
1d
Context
Found during GitLab 18β19 API landscape analysis.