Cohorts are always 0
Summary
Our instance's Cohorts page is always displaying 0 even though usage ping is enabled. We are using CE version 11.5.4 - regardless of version though it has always been 0 because I checked before upgrading to our current version.
I'm not sure whether the report shows 0 because it is only looking at users created in the last 12 months while all of our users have been created way past 12 months.
What is the current bug behavior?
When I go to /-/instance_statistics/cohorts
the columns Inactive users
and Cohort total
are always 0. We have a mix of active and inactive users so I don't understand why nothing is showing up.
What is the expected correct behavior?
I expected to see some percentages similar to the documentation for Cohorts.
Relevant logs and/or screenshots
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: RedHatEnterpriseServer 7.6 Current User: git Using RVM: no Ruby Version: 2.4.5p335 Gem Version: 2.7.6 Bundler Version:1.16.6 Rake Version: 12.3.1 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.1 Go Version: unknownGitLab information Version: 11.5.4 Revision: 315df49 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: http://----- HTTP Clone URL: http://-----/some-group/some-project.git SSH Clone URL: git@-----:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers:
GitLab Shell Version: 8.4.1 Repository storage paths: default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab Shell ...GitLab Shell version >= 8.4.1 ? ... OK (8.4.1) hooks directories in repos are links: ... 2/1 ... repository is empty 4/7 ... ok 4/11 ... ok 3/13 ... ok 13/14 ... ok 4/15 ... ok 4/16 ... ok 13/17 ... repository is empty 13/18 ... ok 3/20 ... repository is empty 3/21 ... ok 5/22 ... ok 4/25 ... ok 3/28 ... ok 4/29 ... ok 4/30 ... ok 3/31 ... repository is empty 3/32 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 2/1 ... yes 4/7 ... yes 4/11 ... yes 3/13 ... yes 13/14 ... yes 4/15 ... yes 4/16 ... yes 13/17 ... yes 13/18 ... yes 3/20 ... yes 3/21 ... yes 5/22 ... yes 4/25 ... yes 3/28 ... yes 4/29 ... yes 4/30 ... yes 3/31 ... yes 3/32 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.4.5) Git version >= 2.9.5 ? ... yes (2.18.1) Git user has default SSH configuration? ... skipped (git user is not present / configured) Active users: ... 6
Checking GitLab ... Finished