Skip to content

Commit 1e9798b

Browse files
committed
docs: control plane metrics details
1 parent 2247606 commit 1e9798b

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

docs/04-For Operators/05-monitoring.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,10 @@ control plane.
8787
### Control-Plane Metrics
8888

8989
In-cluster components are scraped by Prometheus via `ServiceMonitor` resources (pull model).
90-
Alloy self-metrics use a different approach: the control-plane Alloy DaemonSet and all Gardener seed Alloy instances push their metrics via `prometheus.remote_write` to Thanos Receive (`monitoring_thanos_receive_enabled: true`), removing the need for Prometheus to reach into each cluster.
90+
Alloy self-metrics use a different approach — no ServiceMonitor required:
91+
92+
- The **control-plane Alloy** DaemonSet pushes metrics via `prometheus.remote_write` to the in-cluster Thanos Receive. Wired automatically when `monitoring_thanos_receive_enabled: true`.
93+
- **Gardener seed Alloy** instances have no local Prometheus, so they push metrics to the control-plane Thanos Receive ingress instead. Wired automatically when `monitoring_thanos_receive_ingress_enabled: true`.
9194

9295
Metrics are supplied by
9396

0 commit comments

Comments
 (0)