Servicemonitor kubernetes documentation. It brings dynamic, declarative monitoring to your clusters—fully compatible with GitOps workflows and Helm-based deployments. It is one of the primary references when we talk about monitoring in a cloud-native environment and is specially focused on the Kubernetes ecosystem. com Dec 18, 2022 · Service Monitor is a CRD provided by Prometheus Operator, which provides configuration on how provided services should be monitored. Prometheus Operator automatically adds relabelings for a few standard Kubernetes fields. The resource defines via label and namespace selectors which ServiceMonitor, PodMonitor, Probe and PrometheusRule objects should be associated to the deployed Prometheus instances. You can use the ScrapeConfig CRD to scrape targets external to the Kubernetes cluster or to create scrape configurations that are not possible with the higher-level ServiceMonitor, Probe, or PodMonitor resources. Also make sure to add the release Label to the Service and Deployment file too, in the metadata & Specs section. Oct 25, 2018 · Make sure you add the correct Release Label by checking in the ServiceMonitor of Prometheus itself. Sep 28, 2023 · Since there seems to be a bit confusion about selectors, as per documentation, by default Prometheus Operator defaults to only targeting ServiceMonitor, PodMonitor or ScrapeConfig from it’s own Apr 25, 2022 · ServiceMonitor and PodMonitor are terms that you will start to see more often when talking about using Prometheus. Jan 18, 2025 · Integration of a full metrics pipeline into your Kubernetes implementation is outside the scope of Kubernetes documentation because of the very wide scope of possible solutions. Prometheus operator uses this service monitor and configures itself internally. The choice of monitoring platform depends heavily on your needs, budget, and technical resources. See full list on github. The original scrape job’s name is available via the __tmp_prometheus_job_name label. ScrapeConfig # The ScrapeConfig CRD allows you to define how Prometheus should discover and scrape metrics from target services. Or how we wish to collect metrics from different services. ServiceMonitor and PodMonitor Configuration ServiceMonitors and PodMonitors are both pseudo-CRDs that map the scrape configuration of the Prometheus custom resource. The ServiceMonitor is used to define an application you wish to scrape metrics from within Kubernetes, the controller will action the ServiceMonitors we define and automatically build the required Prometheus configuration. This guide explains how to use PodMonitor and ServiceMonitor objects to monitor targets for a sample application. We have covered a lot about Prometheus in the past articles. Jul 21, 2025 · The ServiceMonitor custom resource is the Kubernetes-native way to configure Prometheus scraping without touching config files. To monitor the application using a ServiceMonitor, we will begin by exposing the application with a Service object that selects all the Pods with the label app set to example-app and specify the port where the metrics are exposed. These configuration objects declaratively specify the endpoints that Prometheus will scrape metrics from. . The Prometheus resource declaratively describes the desired state of a Prometheus deployment, while ServiceMonitor and PodMonitor resources describe the targets to be monitored by Prometheus. ServiceMonitors are more commonly used than PodMonitors, and we recommend them for most use cases. ksqvj qntw oxurji pkfh guvhzwfsz ltlyng rongisd isndb ecaxnbn bcb