diff options
author | Filipa Lacerda <filipa@gitlab.com> | 2017-04-20 13:38:23 +0100 |
---|---|---|
committer | Filipa Lacerda <filipa@gitlab.com> | 2017-04-20 13:38:23 +0100 |
commit | 3a7982464b613276d10f2a74c3b08aa07c8e63c2 (patch) | |
tree | 6362c25a0b8ee7b8a9ae84ad15cbb032a4df1bd2 /doc/user | |
parent | c2e26dc0e61541ff8f68c19931a662bcd2178d3e (diff) | |
parent | f99cc765c7cc20372e2c1c915c40e4a71a1dca15 (diff) | |
download | gitlab-ce-doc-js-side-effetcs.tar.gz |
Merge branch 'master' into doc-js-side-effetcsdoc-js-side-effetcs
* master:
Refactor into .vue files
Adds vue js example application and documentation
Add ES lint support to identify poorly written Promises
Update plantuml.md to add the actual link.
Fixed wording
Fix headings
Add more information in the User cohort documentation
Add CHANGELOG
Port of fix/29125-ee to CE
Do not append issuable state to links with custom anchor
Update plantuml.md to fix wrong introduced in link.
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/admin_area/user_cohorts.md | 21 |
1 files changed, 14 insertions, 7 deletions
diff --git a/doc/user/admin_area/user_cohorts.md b/doc/user/admin_area/user_cohorts.md index 1671487bc8c..e25e7a8bbc3 100644 --- a/doc/user/admin_area/user_cohorts.md +++ b/doc/user/admin_area/user_cohorts.md @@ -1,30 +1,37 @@ # Cohorts > **Notes:** -- [Introduced][ce-23361] in GitLab 9.1. +> [Introduced][ce-23361] in GitLab 9.1. As a benefit of having the [usage ping active](settings/usage_statistics.md), GitLab lets you analyze the users' activities of your GitLab installation. Under `/admin/cohorts`, when the usage ping is active, GitLab will show the monthly cohorts of new users and their activities over time. +## Overview + How do we read the user cohorts table? Let's take an example with the following user cohorts.  -For the cohort of June 2016, 163 users have been created on this server. One -month later, in July 2016, 155 users (or 95% of the June cohort) are still -active. Two months later, 139 users (or 85%) are still active. 9 months later, -we can see that only 6% of this cohort are still active. +For the cohort of June 2016, 163 users have been added on this server and have +been active since this month. One month later, in July 2016, out of +these 163 users, 155 users (or 95% of the June cohort) are still active. Two +months later, 139 users (or 85%) are still active. 9 months later, we can see +that only 6% of this cohort are still active. + +The Inactive users column shows the number of users who have been added during +the month, but who have never actually had any activity in the instance. How do we measure the activity of users? GitLab considers a user active if: + * the user signs in * the user has Git activity (whether push or pull). -### Setup +## Setup -1. Activate the usage ping as defined [in the documentation](settings/usage_statistics.md) +1. [Activate the usage ping](settings/usage_statistics.md) 2. Go to `/admin/cohorts` to see the user cohorts of the server [ce-23361]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23361 |