2017-08-17 22:00:37 +05:30
|
|
|
# Usage statistics
|
|
|
|
|
|
|
|
GitLab Inc. will periodically collect information about your instance in order
|
|
|
|
to perform various actions.
|
|
|
|
|
2017-09-10 17:25:29 +05:30
|
|
|
All statistics are opt-out, you can enable/disable them from the admin panel
|
|
|
|
under **Admin area > Settings > Usage statistics**.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
|
|
|
## Version check
|
|
|
|
|
2018-03-27 19:54:05 +05:30
|
|
|
If enabled, version check will inform you if a new version is available and the
|
|
|
|
importance of it through a status. This is shown on the help page (i.e. `/help`)
|
|
|
|
for all signed in users, and on the admin pages. The statuses are:
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2018-03-27 19:54:05 +05:30
|
|
|
* Green: You are running the latest version of GitLab.
|
|
|
|
* Orange: An updated version of GitLab is available.
|
|
|
|
* Red: The version of GitLab you are running is vulnerable. You should install
|
|
|
|
the latest version with security fixes as soon as possible.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2018-03-27 19:54:05 +05:30
|
|
|
![Orange version check example](img/update-available.png)
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2018-03-27 19:54:05 +05:30
|
|
|
GitLab Inc. collects your instance's version and hostname (through the HTTP
|
|
|
|
referer) as part of the version check. No other information is collected.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
2018-03-27 19:54:05 +05:30
|
|
|
This information is used, among other things, to identify to which versions
|
|
|
|
patches will need to be back ported, making sure active GitLab instances remain
|
|
|
|
secure.
|
|
|
|
|
|
|
|
If you disable version check, this information will not be collected. Enable or
|
|
|
|
disable the version check at **Admin area > Settings > Usage statistics**.
|
2017-08-17 22:00:37 +05:30
|
|
|
|
|
|
|
## Usage ping
|
|
|
|
|
|
|
|
> [Introduced][ee-557] in GitLab Enterprise Edition 8.10. More statistics
|
|
|
|
[were added][ee-735] in GitLab Enterprise Edition
|
|
|
|
8.12. [Moved to GitLab Community Edition][ce-23361] in 9.1.
|
|
|
|
|
|
|
|
GitLab sends a weekly payload containing usage data to GitLab Inc. The usage
|
|
|
|
ping uses high-level data to help our product, 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 view the exact JSON payload in the administration panel.
|
|
|
|
|
|
|
|
### Deactivate the usage ping
|
|
|
|
|
2017-09-10 17:25:29 +05:30
|
|
|
The usage ping is opt-out. If you want to deactivate this feature, go to
|
2017-08-17 22:00:37 +05:30
|
|
|
the Settings page of your administration panel and uncheck the Usage ping
|
|
|
|
checkbox.
|
|
|
|
|
|
|
|
To disable the usage ping and prevent it from being configured in future through
|
|
|
|
the administration panel, Omnibus installs can set the following in
|
|
|
|
[`gitlab.rb`](https://docs.gitlab.com/omnibus/settings/configuration.html#configuration-options):
|
|
|
|
|
|
|
|
```ruby
|
|
|
|
gitlab_rails['usage_ping_enabled'] = false
|
|
|
|
```
|
|
|
|
|
|
|
|
And source installs can set the following in `gitlab.yml`:
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
production: &base
|
|
|
|
# ...
|
|
|
|
gitlab:
|
|
|
|
# ...
|
|
|
|
usage_ping_enabled: false
|
|
|
|
```
|
|
|
|
|
|
|
|
[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
|