Create a Dashboard Data Exploration architecture design document
Problem to solve
Data exploration, previously named visualization designer, has been in development for a while now but hasn't received much dedicated attention. It was initially simply a tool to help users query Product Analytics data specifically, but we've pivoted the requirement to explore to a much more useful tool that can be used to explore any data or events from a GitLab instance that users have access to.
The pivot and scale has meant that we often get the same questions asked on multiple occasions, and there is often confusion on what data exploration is and how we should construct it.
This is becoming even more obvious as we work to decouple the framework from the analytics space and Spike: Dashboard Data Exploration (#525642 - closed).
Proposed solution
We should solidify our thinking into an architecture design document which outlines:
- What the data explorer is and isn't
- Common questions and patterns
- Outlining what documentation we need with clear guidelines and expectations