Service ping data for streaming audit event destinations
Release notes
Problem to solve
Users are adding streaming audit event destinations but we don't have visibility into when or how often that is. This makes it difficult to understand adoption of this capability.
Proposal
Add service ping data to record for each instance:
- How many streaming audit event destinations are configured.
- This will help us understand the prevalence of multiple destinations vs one. That use case is one we may see if orgs have multiple SIEMs or compliance teams. As we add filtering, this will be a good way to measure that adoption as well.
- How many groups have any streaming audit event destinations defined
- This will help us understand how many users are taking advantage of the streaming audit event feature.
Intended Users
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.
Edited by Sam Kerr