Prometheus Operator Concepts: Difference between revisions
| Line 24: | Line 24: | ||
==<span id='ServiceMonitor'></span>ServiceMonitor Resource== | ==<span id='ServiceMonitor'></span>ServiceMonitor Resource== | ||
A ServiceMonitor is a custom resource | A ServiceMonitor is a custom resource that can be used to specify a monitoring target to the Prometheus server. The ServiceMonitor describes how metrics can be retrieved from a set of [[Kubernetes_Service_Concepts#Service_.28ClusterIP_Service.29|Services]] exposing the monitoring targets' pods. | ||
Revision as of 22:41, 14 October 2020
Internal
Overview
The Operator decouples the deployment of Prometheus instances from the configuration of which targets they are monitoring. The Operator defines two custom resources: Prometheus and ServiceMonitor.
The Operator ensures that for each Prometheus resource there is a set of Prometheus servers that are running with the correct configuration. The operator manages the servers' configuration, including persistent volume claims, number of replicas, the server version, the Alertmanager instances, the monitoring targets and their associated parameters.
The monitoring targets and their parameters can be set manually, but the preferred option is to let the Operator generate the configuration based on declared ServiceMonitor instances.
Custom Resources
Prometheus Resource
The Prometheus resource declares a "serviceMonitorSelector":
apiVersion: monitoring.coreos.com/v1
kind: Prometheus
...
spec:
serviceMonitorSelector:
matchLabels:
release: prometheus
ServiceMonitor Resource
A ServiceMonitor is a custom resource that can be used to specify a monitoring target to the Prometheus server. The ServiceMonitor describes how metrics can be retrieved from a set of Services exposing the monitoring targets' pods.
The labels are important, they must match Prometheus serviceMonitorSelector.
The current service monitor list can be obtained with:
kubectl -n <namespace> get servicemonitors