diff options
author | Job van der Voort <jobvandervoort@gmail.com> | 2017-05-03 14:24:38 +0100 |
---|---|---|
committer | Job van der Voort <jobvandervoort@gmail.com> | 2017-05-03 14:24:38 +0100 |
commit | f2f159e3605f916ca7cc338c4547fa2cef8502a1 (patch) | |
tree | 219cd5a1ce7c55c5d4b5f9ae3c3700a03923fb66 | |
parent | 1d2b2bd989b270412ef4a23b260d5b9f451214ea (diff) | |
download | gitlab-ce-usage-ping-doc-update.tar.gz |
update the documentation to reflect upcoming changes to the usage pingusage-ping-doc-update
-rw-r--r-- | doc/user/admin_area/settings/usage_statistics.md | 77 |
1 files changed, 6 insertions, 71 deletions
diff --git a/doc/user/admin_area/settings/usage_statistics.md b/doc/user/admin_area/settings/usage_statistics.md index 733e70ca9bf..b9a77813e60 100644 --- a/doc/user/admin_area/settings/usage_statistics.md +++ b/doc/user/admin_area/settings/usage_statistics.md @@ -28,75 +28,10 @@ for all signed in users. [were added][ee-735] in GitLab Enterprise Edition 8.12. [Moved to GitLab Community Edition][ce-23361] in 9.1. -GitLab Inc. can collect non-sensitive information about how GitLab users -use their GitLab instance upon the activation of a ping feature -located in the admin panel (`/admin/application_settings`). +GitLab sends a weekly payload containing usage data to GitLab Inc. The usage +ping uses high-level data to help our support and sales teams. It does not send +any project names, usernames, or any other specific data. The information from +the usage ping is not anonymous, it is linked to the hostname of the instance. -You can see the **exact** JSON payload that your instance sends to GitLab -in the "Usage statistics" section of the admin panel. - -Nothing qualitative is collected. Only quantitative. That means no project -names, author names, comment bodies, names of labels, etc. - -The usage ping is sent in order for GitLab Inc. to have a better understanding -of how our users use our product, and to be more data-driven when creating or -changing features. - -The total number of the following is sent back to GitLab Inc.: - -- Comments -- Groups -- Users -- Projects -- Issues -- Labels -- CI builds -- Snippets -- Milestones -- Todos -- Pushes -- Merge requests -- Environments -- Triggers -- Deploy keys -- Pages -- Project Services -- Projects using the Prometheus service -- Issue Boards -- CI Runners -- Deployments -- Geo Nodes -- LDAP Groups -- LDAP Keys -- LDAP Users -- LFS objects -- Protected branches -- Releases -- Remote mirrors -- Uploads -- Web hooks - -Also, we track if you've installed Mattermost with GitLab. -For example: `"mattermost_enabled":true"`. - -More data will be added over time. The goal of this ping is to be as light as -possible, so it won't have any performance impact on your installation when -the calculation is made. - -### Deactivate the usage ping - -By default, 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. - -## Privacy policy - -GitLab Inc. does **not** collect any sensitive information, like project names -or the content of the comments. GitLab Inc. does not disclose or otherwise make -available any of the data collected on a customer specific basis. - -Read more about this in the [Privacy policy](https://about.gitlab.com/privacy). - -[ee-557]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/557 -[ee-735]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/735 -[ce-23361]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23361 +You can view the exact JSON payload in the administration panel +(`/admin/application_settings`). Here you can also disable the usage ping. |