Design: Scale idea for audit event webhooks into a testable prototype
Scope
- What is the (user) problem? Users keeping track of key events find it challenging to ensure that everything necessary is logged and accessible.
- Who are the users? Cameron the Compliance Manager
- Why do users care about this problem? It usually stems from a regulatory audit requirement. Users must present or relay this information as proof to keep their compliance standing.
- What are the pain points today? For events that relate to GitLab, users are constrained to what is captured and presented in the UI.
- How do users feel about it? Users are frequently demanding more events be captured and exposed (fluid list in sheets). They also desire to perform data manipulation, such as filtering, sorting, pivot reporting, graphing, and combining the data with other data sets.
- How is this done today? Some events are captured through GitLab and exposed in the Audit Events feature. Users can discover information there, and if necessary they can export it to a CSV file. To get a holistic picture, some are creating solutions outside of GitLab to aggregate this information together.
- Why is it done this way? Users are having to aggregate data together because GitLab is not covering the full breadth of the demand. There is a technical limitation for performance and storage which makes it difficult to handle these events at scale.
Design problems to breakdown
Q: How might users specify what they want and where it should go?
A: Starting just with the destination URL
Q: What integrations need to be setup to do this?
A: No integrations for the MVC. A commonly used app is Splunk.
Inspiration
Figma →
Setup | 1 hook |
---|---|
Edited by Austin Regnery