Prometheus Operator Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* [[Prometheus_Concepts#Prometheus_Operator|Prometheus Concepts]] | * [[Prometheus_Concepts#Prometheus_Operator|Prometheus Concepts]] | ||
=Overview= | =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|Prometheus]] and [[#ServiceMonitor|ServiceMonitor]]. | The Operator decouples the deployment of Prometheus instances from the configuration of which [[Prometheus_Concepts#Target|targets]] they are monitoring. The Operator defines two custom resources: [[#Prometheus|Prometheus]] and [[#ServiceMonitor|ServiceMonitor]]. | ||
=Custom Resources= | =Custom Resources= | ||
Revision as of 22:17, 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.
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
The labels are important, they must match Prometheus serviceMonitorSelector.
The current service monitor list can be obtained with:
kubectl -n <namespace> get servicemonitors