Commit 572806d8 authored by Eugene McCrann's avatar Eugene McCrann
Browse files

Remove of Customer Success from Operational Data Collection

parent 017edefd
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
@@ -33,7 +33,7 @@ The first exception is in the collection of hostname and IP address for Self-Man

*Types of Data*: Service Ping Metrics have been broken down into the four categories of Metrics listed below:

- **Operational Data**: Operational Data is a collection of aggregated usage and true/false Metrics that we are contractually obligated to collect in order to render Customer Success Services. Operational Data tracks how value is delivered through the use of the Software and provides insights into optimal customer implementation.
- **Operational Data**: Operational Data is a collection of aggregated usage and true/false Metrics that GitLab mandates in order to optimize the functionality and performance of the Software. Operational Data tracks how value is delivered through the use of the Software and provides insights into optimal customer implementation. These Metrics are integral to GitLab's ability to deliver a well-functioning product and are collected regardless of whether a customer has subscribed to Success Tiers.

   A full list of the Operational Data collected can be viewed [here](https://metrics.gitlab.com/?category=operational).

@@ -53,7 +53,7 @@ The first exception is in the collection of hostname and IP address for Self-Man

- **Operational Data**
  - <ins>Free Self-Managed instances (CE or EE Distribution)</ins>: Operational Data is not collected since the purpose of these Metrics are to assist customers with optimal use of the Software.
  - <ins>Paid Self-Managed instances (EE Distribution) and Dedicated </ins>: Operational Data is intended to be required and configuration is connected to your paid license. If you wish to opt-out you can speak with a GitLab sales representative or [contact support](https://support.gitlab.com/hc/en-us/requests/new).  If your instance is on an [Offline License](/handbook/support/license-and-renewals/workflows/self-managed/cloud-licensing/#cloud-licensing-exemptions), GitLab will not automatically collect Operational Data as long as the instance has followed the instructions for [disabling Service Ping](https://docs.gitlab.com/ee/administration/settings/usage_statistics.html#enable-or-disable-optional-data-in-service-ping).
  - <ins>Paid Self-Managed instances (EE Distribution) and Dedicated </ins>: Operational Data is intended to be required and configuration is connected to your paid license. As this data is necessary to operate and improve the Software, opt-out is not available for most paid deployments. However, if your instance is on an [Offline License](/handbook/support/license-and-renewals/workflows/self-managed/cloud-licensing/#cloud-licensing-exemptions), GitLab will not automatically collect Operational Data as long as the instance has followed the instructions for [disabling Service Ping](https://docs.gitlab.com/ee/administration/settings/usage_statistics.html#enable-or-disable-optional-data-in-service-ping).
  - <ins>Free and Paid GitLab.com users</ins>: Global Privacy Control ("GPC") signals may prevent the collection of certain Operational Data Metrics that relate to browser level aggregate totals, such as the number of times a button was clicked by a user with GPC signals enabled. However, please note that GPC signals depend on how the event is triggered and thus may not be recognized in all situations. Further, GPC signals will not prevent the collection of downstream non-synchronous Metrics. For  example, if a user with GPC enabled signals clicks a button to start a CI job, this button click will not be tracked. But if the same user pushes new code to a repository, thereby inciting an automated run of the same job, this run will be counted since it occurred non-synchronously from the user's direct action. Any other interactions that happen outside of the browser, such as a direct call to GitLab's API, may also be included in the Metrics.
- **Optional Data**:
  - <ins>Free and Paid Self-Managed instances (CE or EE distribution) or Dedicated</ins>: These Metrics are collected by default. Optional Data can be disabled through an in-app admin setting or through modifying the configuration file.  Please [visit our documentation](https://docs.gitlab.com/ee/administration/settings/usage_statistics.html#enable-or-disable-optional-data-in-service-ping) to learn more.