This epic contains issues that can quickly help GitLab move towards a more robust usage ping collection service. These issues should be straightforward and ideally all be completed within one quarter. If they turn out to be more complex than anticipated, they will be broken down into smaller MVC's. #### What problems does this epic solve? It's difficult to make decisions based on usage data analysis in its current state: * Usage ping data is unreliable due to frequently missed data. * The metrics we have available are basic and don't provide enough insight on how GitLab is being used. * Usage ping is badly documented and confusing to work with, both as a developer and an end user. #### Future state * Robust, higher integrity usage ping data. * A clearer process on how to interact with and inject usage ping into GitLab.