Package AMAU: Measure adoption of the GitLab Dependency Proxy
Problem to solve
In the past several milestones the GitLab Dependency Proxy has moved to Core, added support for private projects, and added features that help you to avoid Docker Hub rate limits. We've seen increased engagement from the GitLab Community, but currently, the only data that we have with regards to the Dependency Proxy is how many projects have the feature enabled. Now that private projects are supported and the feature is enabled by default, this number will naturally increase. However, it would be difficult to understand from that metric if the feature is being used and how frequently.
Proposal
Measure adoption of the Dependency Proxy using the following metrics:
Activity counters
- A count of the number of container images pulled on GitLab.com. We would like to view this activity data by day, week, and month. We would like to distinguish between when an image is pulled from Docker Hub vs. the cache.
- Measure the total storage usage and storage cost of the proxy's cache on GitLab.com.
- A count of events for each time the Dependency Proxy's cache is cleared for a group on GitLab.com.
AMAU
Measure user-level adoption of the feature via the usage ping to help drive the Package group's SMAU/GMAU.
- The number of users that pull container images on pinging instances. Again we'd like to view this data by day, week, and month. And we'd like to distinguish between images pulled from Docker Hub vs. the cache. This will inform our hit ratio for users, or how often is the image pulled from the cache.
- Since many of these images will be pulled using a token, we should count deploy, job, personal access token as user types.
Dashboard and Performance Indicators
The new userfied data should be added to the Package group's dashboard as a new AMAU metric. It should also be added as such to the Ops Performance Indicators.