From ae848576f6b23217a3aaf1a6611cbf32084645cd Mon Sep 17 00:00:00 2001
From: Jon Glassman <jglassman@gitlab.com>
Date: Thu, 27 Feb 2025 22:36:31 +0000
Subject: [PATCH] Add intro from Claude
---
.../monitoring/prometheus/web_exporter.md | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/administration/monitoring/prometheus/web_exporter.md b/doc/administration/monitoring/prometheus/web_exporter.md
index 84d096538d0f8..b23d3b77afde4 100644
--- a/doc/administration/monitoring/prometheus/web_exporter.md
+++ b/doc/administration/monitoring/prometheus/web_exporter.md
@@ -12,6 +12,17 @@ title: Web exporter (dedicated metrics server)
{{< /details >}}
+Improve reliability and performance of your GitLab monitoring by collecting metrics
+separately from your main application server. A dedicated metrics server isolates
+monitoring traffic from user requests, preventing metrics collection from impacting
+application performance.
+
+For medium to large installations, this separation can provide more consistent data
+collection during peak usage times and can reduce the risk of missing critical metrics
+during high load periods.
+
+## How GitLab metrics collection works
+
When [monitoring GitLab with Prometheus](_index.md), GitLab runs various collectors that
sample the application for data related to usage, load and performance. GitLab can then make
this data available to a Prometheus scraper by running one or more Prometheus exporters.
--
GitLab