ConvDevIndex: Data is still calculating...

Summary

Im using gitlab in a docker container behind a proxy. I´ve noticed that the ConvDev monitoring isn´t working. I still get after a few days the message Data is still calculating

Steps to reproduce

Run gitlab container behind a reverse proxy

What is the current bug behavior?

Monitoring isn't displayed

What is the expected correct behavior?

See monitoring metrics

Relevant logs and/or screenshots

See attachedConvDev_Index___Admin_Area___GitLab

Results of GitLab environment info

Expand for output related to GitLab environment info 
docker exec -it gitlab_web_1 gitlab-rake gitlab:env:info


System information
System:
Current User:	git
Using RVM:	no
Ruby Version:	2.3.3p222
Gem Version:	2.6.6
Bundler Version:1.13.7
Rake Version:	12.0.0
Redis Version:	3.2.5
Git Version:	2.13.5
Sidekiq Version:5.0.4
Go Version:	unknown


GitLab information
Version:	9.5.4
Revision:	fbffc27
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		http://nas-10-gitlab:8888
HTTP Clone URL:	http://nas-10-gitlab:8888/some-group/some-project.git
SSH Clone URL:	ssh://git@nas-10-gitlab:2224/some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no


GitLab Shell
Version:	5.8.0
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 
docker exec -it gitlab_web_1 sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...


GitLab Shell version >= 5.8.0 ? ... OK (5.8.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/4 ... ok
2/5 ... ok
2/7 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Reply by email ...


Reply by email is disabled in config/gitlab.yml


Checking Reply by email ... Finished


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/4 ... yes
2/5 ... yes
2/7 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.3)
Git version >= 2.7.3 ? ... yes (2.13.5)
Active users: ... 2


Checking GitLab ... Finished


(we will only investigate if the tests are passing)

Possible fixes

modify nginx-proxy file?

Spec

On the Conversational Development Index page, if usage ping is not activated:

  • The "Data is still calculating" message is not displayed
  • A message is displayed saying:

Please activate usage ping

Your GitLab instance’s usage ping must be activated in order to use this feature. Please see the feature documentation to learn more.

Edited by Dan Jensen