View the TAM Handbook homepage for additional TAM-related handbook pages.
Usage ping generates customer analytics on self-managed instances that enable GitLab to collaborate with our customers to accelerate value attribution, achieve return-on-investment (ROI) goals, and accomplish business outcomes with the GitLab solution. Specifically, it helps GitLab understand product adoption to:
For the definition of each metric, please see our Usage Ping Metrics Dictionary.
Usage Ping provides insights into your teams’ usage of GitLab to enable you to understand output, maturity, and potential improvement areas across your instance. In understanding these key platform usage metrics, we can together be strategic in our roadmap for enablement and growth planning.
GitLab can collaborate with you to understand your security controls and regulatory requirements that you have to meet. We've seen several risk-mitigating solutions where similar concerns regarding "outbound data transfers", and data leaving a secured boundary. Are there specific team members from security/compliance/privacy organizations that might provide additional insights? We understand your concerns and would be happy to have a call with our respective security teams to help resolve issues you may have. Before our call, GitLab will request you provide the specific compliance requirements you may have.
Yes, you are able to extract this information manually and review prior to sending to GitLab. Here are the steps:
At this time, it will be a manual process to save each ping and analyze the metrics over time. We are starting to explore the possibilities to enable customer visualization and/or analysis.
Our documentation shows all usage statistics and content that is sent back to GitLab. When we change / update product analytics you can view the exact JSON payload in the administration panel. To view the payload: Navigate to the Admin Area > Settings > Metrics and profiling. Expand the Usage statistics section. Click the Preview payload button.
You can inspect the data and have your security team review it. They can continue to monitor (via ELK stack) that GitLab is not breaking security policy with new releases. We invite you to ship this data to an internal ELK stack, and sanitize it before sending to your GitLab Technical Account Manager. If we can get your security team to review and approve, we can fully automate this process so you don't have to go to the trouble.
We respect your organizations' network security policies and restrictions and understand there are situations where it is not feasible or technically possible to submit usage ping over the Internet. If Usage Ping is blocked by a firewall, load balancer, or proxy, you might consider modifying your network configuration to un-block the Usage ping payload from being sent to GitLab.
If you see value in sharing Usage Ping data and it’s not technically possible for you to do so directly, GitLab can provide you instructions to share the data manually, including allowing you to sanitize certain data as preferred.
The usage ping is opt-out. If you want to deactivate this feature, go to the Settings page of your administration panel and uncheck the Usage ping checkbox. You can view the payload at "/admin/application_settings/metrics_and_profiling" in the Usage Statistics section and press the "View Payload" button.
Product Documentation: Deactivate the Usage Ping
Important Documentation links