Log auto stop environment actions
Problem to solve
In #20956 (closed) we introduced the ability to auto stop an environment after a configured amount of time. This action is not logged in the audit log, but should be.
Intended users
Users who need this info for compliance, auditing and monitoring of user actions:
Further details
- Use Case 1 upon request for auto-stops, a user should be able to review auto-stops logged per environment
-
Use Case 2 Downloads for audit logs should be include
auto stop
events
Proposal
Add to the audit log an action for auto stop environment as defined below on stop
of the environment (when the expiry time comes)
Author | Action | Target | At |
---|---|---|---|
Automatic |
"Auto Stop environment" | <environment name> |
<timestamp> |
Permissions and Security
- Changes to audit logs should follow the normal access/permissions of Audit Logs at GitLab
- Downloads of audit logs should follow the normal access/permissions of Audit Logs at GitLab
- Guests/non-GitLab users should not be able to download, edit, or change audit logs
Documentation
- Audit Events Documentation - for audit events permissions and implementation
- Log System Documentation - Administrations of Audit Logs
Testing
- This audit log content needs to be
view only
by all users, withedit log
permissions following the audit log permission structure - Start tracking of environments deployments/stops behind a feature flag
What does success look like, and how can we measure that?
- The usage of this feature will be related to the downloads of the audit logs, so we should see an increase in audit log downloads for releases when these items are added
- % increase in MAU for release audit logs
What is the type of buyer?
- Community Edition
Links / references
- #20956 (closed) - Auto-Stop Issue
Edited by 🤖 GitLab Bot 🤖