From 3ee8728a81af21c43451e99af6ed67ac0795a34b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Muhamed=20Huseinba=C5=A1i=C4=87?= Date: Mon, 20 Jul 2020 11:04:32 +0000 Subject: [PATCH] Add details around /git_process endpoint for Omnibus --- .../monitoring/prometheus/gitlab_exporter.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/doc/administration/monitoring/prometheus/gitlab_exporter.md b/doc/administration/monitoring/prometheus/gitlab_exporter.md index 686ed14ba42889..544f71f3427ac4 100644 --- a/doc/administration/monitoring/prometheus/gitlab_exporter.md +++ b/doc/administration/monitoring/prometheus/gitlab_exporter.md @@ -30,4 +30,18 @@ To enable the GitLab exporter in an Omnibus GitLab instance: for the changes to take effect. Prometheus automatically begins collecting performance data from -the GitLab exporter exposed at `localhost:9168`. +the GitLab exporter metrics exposed at `localhost:9168/metrics`. + +Note that GitLab Exporter, in additon to /metrics endpoint, also exposes the following endpoints: + +/database +/git_process +/process +/sidekiq + +All of them combined are making up the /metrics endpoint. + +Note that, however, for Omnibus installations, /git_process endpoint is always going to be empty. Metrics +exposed through it (git_pull_time_milliseconds, git_push_time_milliseconds and process_count (for Git processes)) +are not configured out-of-the-box for Omnibus installations and are outside of scope for support for now. You are +more than welcome to play around with the exporter configuration on your own though to make them work for your instance. -- GitLab