https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/Recent content in Developer Guide on Prometheus OperatorHugo -- gohugo.ioen-UShttps://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/getting-started/This guide explains how to use PodMonitor and ServiceMonitor objects to monitor targets for a sample application. 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. Pre-requisites # Before you begin, ensure that you have: A Kubernetes cluster with admin permissions A running Prometheus Operator (refer to the Installation page) A running Prometheus instance (refer to the Platform Guide) Deploying a sample application # First, let’s deploy a simple example application with 3 replicas which listens and exposes metrics on port 8080.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/alerting/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/alerting/This guide assumes you already have a basic understanding of the Prometheus Operator and have gone through the Getting Started guide. We’re also expecting you to know how to run an Alertmanager instance. In this guide, we’ll explore the various methods for managing Alertmanager configurations within your Kubernetes cluster. Prometheus’ configuration also includes “rule files”, which contain the alerting rules. When an alerting rule is triggered, it fires that alert to all Alertmanager instances, on every rule evaluation interval.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/scrapeconfig/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/scrapeconfig/Starting with prometheus-operator v0.65.x, one can use the ScrapeConfig CRD to scrape targets external to the Kubernetes cluster or create scrape configurations that are not possible with the higher level ServiceMonitor/Probe/PodMonitor resources. Prerequisites # prometheus-operator >v0.65.1 ScrapeConfig CRD installed in the cluster. Make sure to (re)start the operator after the CRD has been created/updated. Configure Prometheus or PrometheusAgent to select ScrapeConfigs # Both the Prometheus and PrometheusAgent CRD have a scrapeConfigSelector field.https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/scrapeclass/Mon, 01 Jan 0001 00:00:00 +0000https://deploy-preview-154--sleepy-hopper-0fdb6b.netlify.app/docs/developer/scrapeclass/Prerequisites # Before you begin, ensure that you have: Prometheus-Operator > v0.73.0 A running Prometheus or PrometheusAgent instance. Introduction # ScrapeClass is a feature that allows you to define common configuration settings to be applied across all scrape resources( PodMonitor, ServiceMonitor, ScrapeConfig and Probe ). This feature is similar to StorageClass in Kubernetes and is very useful when it comes to standardising configurations such as common relabelling rules, TLS certificates and authentication.