Service Ping FAQ

1. You are here:
2. Customer Success
3. Customer Success Management Handbook
4. Service Ping FAQ

On this page

• What is Service Ping
• How Does Service Ping Help Me?
• Commonly Asked Questions and Concerns
  • 1. What information is sent via service ping?
  • 2. It's a corporate security policy that we don't send data to vendors.
  • 3. Is there a way we can share this data manually so that we can review it before it goes out?
• 4. Can customers visualize the data?
• 5. How do we ensure that you don't change what's in the payload to include things we don't want to share? How do we re-verify this with each new release in a way that doesn't take a lot of time or effort?
• 6. Our security team will have to sign off first
• 7. We have network isolation and there is no way for usage to get out of their network
• 8. How do I disable service ping?

View the CSM Handbook homepage for additional CSM-related handbook pages.

---

What is Service Ping

Service 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:

1. Ensure adoption is aligned to business outcomes (i.e., goals, timelines, etc).
2. Understand usage for industry and best practice recommendations
3. Recommend features or capabilities that maximize solution value based on:
   • Gaps in adoption
   • New features or capabilities that can be leveraged
4. Enable User Cohorts and GitLab DevOps Score that provides an overview of customers’ adoption of Concurrent DevOps from planning to monitoring
5. Track usage and adoption over time

For the definition of each metric, please see our Service Ping Metrics Dictionary.

Links to other ways Service Ping is used by Customer Success

How Does Service Ping Help Me?

Service 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.

• As a benefit of having the service ping active, GitLab lets you analyze the users’ activities over time of your GitLab installation.
• As a benefit of having the service ping active, GitLab provides you with The DevOps Score, which gives you an overview of your entire instance’s adoption of Concurrent DevOps from planning to monitoring.
• You will get better, more proactive guidance when working with a Customer Success Manager.
• You will get insight and advice into how to get the most value out of their investment in GitLab.
• You get a report that illustrates how they compare against other similar organizations (anonymized), with specific advice and recommendations on how to improve their DevOps processes.

Commonly Asked Questions and Concerns

1. What information is sent via service ping?

GitLab collects product usage data from self-managed GitLab instances (Community Edition and Enterprise Edition) through a service ping, you can view a sample here. Please see GitLab Privacy Policy for additional details.

2. It's a corporate security policy that we don't send data to vendors.

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.

3. Is there a way we can share this data manually so that we can review it before it goes out?

Yes, you are able to extract this information manually and review prior to sending to GitLab. Here are the steps:

1. Login to your gitlab instance as administrator
2. Navigate to the admin section of the Interface by clicking the "wrench" at the top navigation ribbon of the homepage
3. At the left navigation panel, hover over the "Settings" –> and click on "Metrics and Profiling"
4. When the Metrics and Profiling page populates, scroll down to the "Usage Statistics" segment of the page and click on the "Expand" button at the right-hand side.
5. Click on "Preview payload" button
6. A JSON formatted output of the data that is sent from GitLab instances to gitlab.com when allowed will be displayed in a pop-up. Copy and paste this information into a text file, encrypt and send to GitLab or upload over SSH/HTTPS to the customer collaboration for your organization that's securely hosted on gitlab.com

4. Can customers visualize the data?

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.

5. How do we ensure that you don't change what's in the payload to include things we don't want to share? How do we re-verify this with each new release in a way that doesn't take a lot of time or effort?

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.

6. Our security team will have to sign off first

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 Customer Success 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.

7. We have network isolation and there is no way for usage to get out of their network

We respect your organizations' network security policies and restrictions and understand there are situations where it is not feasible or technically possible to submit service ping over the Internet. If Service Ping is blocked by a firewall, load balancer, or proxy, you might consider modifying your network configuration to un-block the Service Ping payload from being sent to GitLab.

If you see value in sharing Service 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.

8. How do I disable service ping?

The service ping is opt-out. If you want to deactivate this feature, go to the Settings page of your administration panel and uncheck the Service 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 Service Ping

Important Documentation links

1. Admin Settings for Service Ping
2. Usage Statistics Collected
3. Network Configuration