Include event_type in the JSON payload of a streaming audit event

Full context in parent epic

Release notes

Problem to solve

It can be challenging to understand what type of data a streaming audit event will contain without parsing the entire message. This is complicated, time-consuming, and error prone code to write. Additionally, it is not always possible to look at the audit event type HTTP header, since the headers may be gone by the time a portion of code has access to the JSON payload of a message.

Proposal

Update streaming audit events to include the event_type value in the JSON payload. This value should match the x-gitlab-audit-event-type that is sent in the event's HTTP header.

Intended users

Feature Usage Metrics

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.