mirrors/prometheus-operator
mirrors/prometheus-operator
1
0
Fork 0
mirror of https://github.com/prometheus-operator/prometheus-operator.git synced 2025-04-21 03:38:43 +00:00
Code Activity

docs: Improve ServiceMonitor namespace relation documentation ()

Browse source 
ServiceMonitors must be installed in the same namespace as the Prometheus, if ServiceMonitorNamespaceSelector is not specified.
This commit is contained in:
Ismail Kaboubi 2018-06-14 09:33:24 +02:00 • committed by Max Inden
parent 4fac63a25b
commit e261501a36
1 changed files with 1 additions and 1 deletions

2
Documentation/user-guides/getting-started.md
View file

@ -157,7 +157,7 @@ The Prometheus resource declaratively describes the desired state of a Prometheu
![Prometheus Operator Architecture](images/architecture.png "Prometheus Operator Architecture")
The Prometheus resource includes a field called `serviceMonitorSelector`, which defines a selection of ServiceMonitors to be used.
The Prometheus resource includes a field called `serviceMonitorSelector`, which defines a selection of ServiceMonitors to be used. By default and before the version `v0.19.0`, ServiceMonitors must be installed in the same namespace as the Prometheus instance. With the Prometheus Operator `v0.19.0` and above, ServiceMonitors can be selected outside the Prometheus namespace via the `serviceMonitorNamespaceSelector` field of the Prometheus resource.
First, deploy three instances of a simple example application, which listens and exposes metrics on port `8080`.