diff options
Diffstat (limited to 'doc/user/admin_area/analytics')
-rw-r--r-- | doc/user/admin_area/analytics/convdev.md | 5 | ||||
-rw-r--r-- | doc/user/admin_area/analytics/dev_ops_report.md | 29 | ||||
-rw-r--r-- | doc/user/admin_area/analytics/img/cohorts_v13_4.png | bin | 0 -> 92729 bytes | |||
-rw-r--r-- | doc/user/admin_area/analytics/img/dev_ops_report_v13_4.png | bin | 0 -> 167541 bytes | |||
-rw-r--r-- | doc/user/admin_area/analytics/index.md | 10 | ||||
-rw-r--r-- | doc/user/admin_area/analytics/user_cohorts.md | 29 |
6 files changed, 73 insertions, 0 deletions
diff --git a/doc/user/admin_area/analytics/convdev.md b/doc/user/admin_area/analytics/convdev.md new file mode 100644 index 00000000000..3ffda3f4400 --- /dev/null +++ b/doc/user/admin_area/analytics/convdev.md @@ -0,0 +1,5 @@ +--- +redirect_to: 'dev_ops_report.md' +--- + +This document was moved to [another location](dev_ops_report.md). diff --git a/doc/user/admin_area/analytics/dev_ops_report.md b/doc/user/admin_area/analytics/dev_ops_report.md new file mode 100644 index 00000000000..f04bd69b76b --- /dev/null +++ b/doc/user/admin_area/analytics/dev_ops_report.md @@ -0,0 +1,29 @@ +# DevOps Report + +> - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/30469) in GitLab 9.3. +> - [Renamed from Conversational Development Index](https://gitlab.com/gitlab-org/gitlab/-/issues/20976) in GitLab 12.6. + +NOTE: **Note:** +Your GitLab instance's [usage ping](../settings/usage_statistics.md#usage-ping) must be activated in order to use this feature. + +The DevOps Report gives you an overview of your entire instance's adoption of +[Concurrent DevOps](https://about.gitlab.com/topics/concurrent-devops/) +from planning to monitoring. + +## DevOps Score + +DevOps Score displays the usage of GitLab's major features on your instance over +the last 30 days, averaged over the number of active users in that time period. It also +provides a Lead score per feature, which is calculated based on GitLab's analysis +of top-performing instances based on [usage ping data](../settings/usage_statistics.md#usage-ping) that GitLab has +collected. Your score is compared to the lead score of each feature and then expressed as a percentage at the bottom of said feature. +Your overall **DevOps Score** is an average of your feature scores. You can use this score to compare your DevOps status to other organizations. + +![DevOps Report](img/dev_ops_report_v13_4.png) + +The page also provides helpful links to articles and GitLab docs, to help you +improve your scores. + +Usage ping data is aggregated on GitLab's servers for analysis. Your usage +information is **not sent** to any other GitLab instances. If you have just started using GitLab, it may take a few weeks for data to be +collected before this feature is available. diff --git a/doc/user/admin_area/analytics/img/cohorts_v13_4.png b/doc/user/admin_area/analytics/img/cohorts_v13_4.png Binary files differnew file mode 100644 index 00000000000..4af1841a033 --- /dev/null +++ b/doc/user/admin_area/analytics/img/cohorts_v13_4.png diff --git a/doc/user/admin_area/analytics/img/dev_ops_report_v13_4.png b/doc/user/admin_area/analytics/img/dev_ops_report_v13_4.png Binary files differnew file mode 100644 index 00000000000..1fa070a6915 --- /dev/null +++ b/doc/user/admin_area/analytics/img/dev_ops_report_v13_4.png diff --git a/doc/user/admin_area/analytics/index.md b/doc/user/admin_area/analytics/index.md new file mode 100644 index 00000000000..b3336b471f8 --- /dev/null +++ b/doc/user/admin_area/analytics/index.md @@ -0,0 +1,10 @@ +# Instance-level analytics + +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41416) in GitLab 11.2. + +Administrators have access to instance-wide analytics, as shown in **Admin Area > Analytics**. + +There are two kinds of statistics: + +- [DevOps Report](dev_ops_report.md): Provides an overview of your entire instance's feature usage. +- [User Cohorts](user_cohorts.md): Display the monthly cohorts of new users and their activities over time. diff --git a/doc/user/admin_area/analytics/user_cohorts.md b/doc/user/admin_area/analytics/user_cohorts.md new file mode 100644 index 00000000000..faf8caa7e00 --- /dev/null +++ b/doc/user/admin_area/analytics/user_cohorts.md @@ -0,0 +1,29 @@ +# Cohorts + +> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/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 over time of your GitLab installation. + +## Overview + +How do we read the user cohorts table? Let's take an example with the following +user cohorts. + +![User cohort example](img/cohorts_v13_4.png) + +For the cohort of March 2020, three users have been added on this server and have +been active since this month. One month later, in April 2020, two users are +still active. Five months later (August), we can see that one user from this cohort +is active, or 33% of the original cohort of three that joined in March. + +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). +- The user visits pages related to Dashboards, Projects, Issues, and Merge Requests ([introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/54947) in GitLab 11.8). +- The user uses the API +- The user uses the GraphQL API |