Skip to content

Commit 8223769

Browse files
authored
docs: Clarify where to deploy a custom Prometheus (gardener#656)
1 parent 606d0c4 commit 8223769

File tree

1 file changed

+2
-2
lines changed
  • website/documentation/getting-started/observability

1 file changed

+2
-2
lines changed

website/documentation/getting-started/observability/alerts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ spec:
2424
2525
For more information, see [Alerting](https://github.com/gardener/gardener/blob/master/docs/monitoring/alerting.md).
2626
27-
### Custom Alerts - Federation
27+
### Custom Alerts Federation
2828
29-
If you need more customization for alerts for control plane metrics, you have the option to deploy your own Prometheus into your shoot control plane.
29+
If you need more customization for alerts for control plane metrics, you have the option to deploy your own Prometheus into your shoot cluster.
3030
3131
Then you can use federation, which is a Prometheus feature, to forward the metrics from the Gardener managed Prometheus to your custom deployed Prometheus. Since as a shoot owner you do not have access to the control plane pods, this is the only way to get those metrics.
3232

0 commit comments

Comments
 (0)