[#21968] Prometheus operator ServiceMonitor discovery docs improvement (#21982)

* [#21968] Prometheus operator ServiceMonitor discovery docs improvement

Signed-off-by: Luca Prete <preteluca@gmail.com>

* Bump up chart version

Signed-off-by: Luca Prete <preteluca@gmail.com>
This commit is contained in:
Luca Prete
2020-04-17 23:15:56 -07:00
committed by GitHub
parent 0cf1c3ee57
commit 01d380a358
+3
View File
@@ -129,6 +129,9 @@ If this error has already been encountered, a `helm history` command can be used
## prometheus.io/scrape
The prometheus operator does not support annotation-based discovery of services, using the `serviceMonitor` CRD in its place as it provides far more configuration options. For information on how to use servicemonitors, please see the documentation on the coreos/prometheus-operator documentation here: [Running Exporters](https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/running-exporters.md)
By default, Prometheus discovers ServiceMonitors within its namespace, that are labeled with the same release tag as the prometheus-operator release.
Sometimes, you may need to discover custom ServiceMonitors, for example used to scrape data from third-party applications. An easy way of doing this, without compromising the default ServiceMonitors discovery, is allowing Prometheus to discover all ServiceMonitors within its namespace, without applying label filtering. To do so, you can set `prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues` to `false`.
## Configuration
The following tables list the configurable parameters of the prometheus-operator chart and their default values.