Missing units on Monitoring dashboard graphs
Summary
(Summarize the bug encountered concisely)
The charts/graphs on the Monitoring/Metrics dashboard and Cluster Health do not have units displayed.
Steps to reproduce
(How one can reproduce the issue - this is very important)
- Add a Kubernetes cluster to a project.
- Install Helm and Prometheus.
- Do a deployment to the cluster.
- Open Operations > Metrics.
- Observe the graphs. For example, the memory graphs have no indication if the numbers are MB or GB.
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
No units are displayed on the graphs in the Monitoring dashboard.
What is the expected correct behavior?
(What you should see instead)
Units should be displayed.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)