### Context GitLab uses monthly active users to help make prioritization and investment decisions in given areas of the product. Measuring active users over time can help inform GitLab team members about high-level trends and the adoption of a given feature. For the Package stage, we measure monthly active users, including self-managed, for the Package Registry but not the container registry. ### Problem to solve Not having user-level data for the container registry makes it hard to understand the value of product investments. It also means that we are undervaluing the overall footprint of the Package stage. ### Proposal Add new events to the service ping to count the number of users that have published, downloaded, or deleted a container image/tag. * pushed/updated an image repository * pushed/updated a tag * deleted a tag I'd like the data to be available in SiSense which in turn will filter into the internal handbook. Something like this would be ideal:  So ideally, I would like: 1. A monthly count of users that interacted with the container registry 2. If possible, a weekly count of users that interacted with the container registry 3. A count of events (Self-Managed and SaaS) for each event type by month, if possible by week. For the Package Registry this was all done using Redis for scale. But I'm not sure if that makes sense for the container registry. ### Plan The high-level plan for delivering this was outlined in https://gitlab.com/gitlab-org/gitlab/-/issues/364730#note_1058520288.