Clarify (lack of) retention policy for Audit Events in the docs
What does this MR do and why?
The GitLab Support team has seen a few tickets from customers who want to know what the present retention policy is for Audit Events. As a part of our approach to deflecting tickets through documentation, I am assembling this merge request to introduce an answer to this query to our docs.
There are two issues in our issue tracker about this:
- #216847 Retention strategy for audit events
- #8137 (closed) Specify a retention period for audit events
I have linked to the #8137 (closed) issue because it's older and is associated with the Category:Audit Events but I think it would be similarly reasonable to link to #216847 as it is more recent and has been modified more recently. Regardless, this MR (and updates I plan to add to each issue) will link the two issues together.
🎫 Related Tickets
GitLab team members with access to Zendesk can review tickets around this query.
- https://gitlab.zendesk.com/agent/tickets/254893
- https://gitlab.zendesk.com/agent/tickets/196462
- https://gitlab.zendesk.com/agent/tickets/191356
- https://gitlab.zendesk.com/agent/tickets/178513
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.