Gitlab Prometheus metrics not available

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Describe your question in as much detail as possible:
I have a self-hosted GitLab and I wanted to Generate DORA Metrics Charts in Grafana collecting them with Prometheus. I set up the following configs in the gitlab.rb( The linux distribution)

gitlab_rails['prometheus_enabled'] = true
gitlab_rails['monitoring_whitelist'] = [...]
sidekiq['metrics_enabled'] = true
gitlab_exporter['listen_address'] = '0.0.0.0'
gitlab_exporter['listen_port'] = '[port]'

I also have the Prometheus metrics turned on from the admin panel.

So, for now I am able to run curl http://ip:port/metrics and get metrics but they only consist of sidekiq, ruby, gitlab_database_rows. I miss the key metrics that I need to derive the DORA metrics. I tried to access curl http://ip:port/-/metrics but this returns an error instead.

  • What are you seeing, and how does that differ from what you expect to see?
    I expect to run curl http://ip:port/-/metrics and get the metrics like on curl http://ip:port/metrics but it returns Sinatra doesn't know this ditty. I need help getting access to these metrics.

  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

I have tried reading through the docs but i can’t find the solution.

Configuration

Add the observability configuration relevant to the question.

Versions

Please select whether options apply, and add the version information.

  • Self-managed
  • GitLab.com SaaS
  • Dedicated

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info):

Observability

  • OpenTelemetry SDK version:

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush: