Collect data and usage measures for devops:package
Problem to solve
As a Product Manager of Package, when I am prioritizing features and bugs, I need access to data that measures the adoption and usage of Package features, so that I can make more informed decisions.
Currently in Package, we only track the number of projects with packages. We must identify the important metrics, start tracking them and then add them to a dashboard in Periscope. Our first priority will be to capture general engagement metrics, things like: is the feature active and how many times has it been used. Once we are measuring this data, we will be able to ask better questions and further our data strategy.
- GitLab Product Managers
- GitLab UX Designers
- GitLab Developers
Once we have access to the data, there are a few reporting dashboards that I would like to prioritize:
**Begin to track the following items: **
- Container Registry (on/off)
- Packages (on/off)
- number of packages
- number of images in the container registry
- Dependency Proxy (on/off)
- number of NPM packages
- Registry updated (new packages added, removed, modified)
- number of Maven Packages
- Repository updated (new packages added, removed, modified)
- Container Registry
- number of Docker Images
- Registry updated (new images added, removed, modified)
- Dependency Proxy
- number of items in the proxy
For all of these, we are going to want to slice this data by:
- Account type
- Time period (day/week/month/quarter)
Permissions and Security
The only permissions and security aspects we need to be concerned about are who has access to GitLab data and dashboards. That is currently handled by Periscope and the data team.
What does success look like, and how can we measure that?
Success for this issue will be a merge request which adds the agreed upon KPIs to the GitLab ping metrics. In the future, we will need to prioritize updating and building a package focused dashboard and updating the queries to include the new metrics for the core GitLab dashboards.