### Problem to solve As noted in the parent epic https://gitlab.com/groups/gitlab-org/-/epics/8057: > There are many different audit event types sent from GitLab. It can be difficult to quickly identify what type of event is being sent without complex logic to parse out the `custom_messages`, target types, source types, and other data that exists in the message. Some audit events are named `audit_operation`. This isn't a descriptive name and makes it difficult to differentiated from other events. ### Proposal Add a meaningful `name` for all our audit events that can be used to differentiate it from other events. Naming should follow the `noun_verb` name format and use the past tense. For example `ci_variable_created`. If the `noun` or attribute name starts with a verb then it's fine to use the original name + verb, for example `allow_merge_on_skipped_pipeline_updated`. For events created with `audit_changes` we can pass the event name using the `event_type` argument. ```rb audit_changes(:email, as: 'email address', event_type: 'email_address_added') ``` Also consider [this MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92074) as an example of how to do this. ### Testing You don't need to test these events locally so no EE license is required. Adding or updating unit tests is sufficient for streamed events.