<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve <!-- What is the user problem you are trying to solve with this issue? --> 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. Below attached sheet contains conclusive list of audit events with event type information Sheet: https://docs.google.com/spreadsheets/d/119Dvp2ARsoCo8zVvpoLHdcdfygEVW9kCvbRqyh8DPIg/edit?usp=sharing ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> 1. Add a new HTTP header to all events sent with [streaming audit events](https://docs.gitlab.com/ee/administration/audit_event_streaming.html) to identify the specific type of event that is inside the message. 1. Add a new key/value pair in the event JSON payload to identify the specific type of event that is inside the message. 1. Note: The value in the HTTP header and the JSON should be identical. 1. Update the documentation to include the possible event types that can be sent. 1. Describe and document how to change and upgrade event types in the future 1. _Concept idea: Can we have some fixed numerical value and then implementing a string_lookup function for it? To enable a static value to be put in the code but to iterate on top of the human readable string that is displayed. Could we use an enum?_ _Refinement note: Consider using this [this MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86881) as a starting point._ Note: When considering all the events in the product, [this list](https://docs.google.com/spreadsheets/d/1gTKpZxEwPrzA6EL4oRuILNDs5Aea7186sPoB8okYhdQ/edit#gid=1012769642) may be helpful as a starting point. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->