Custom Scrape Configs & Exporters in Kube-Prometheus-Stack (2026)
Add additionalScrapeConfigs, wire up the Blackbox Exporter for uptime probes, run Pushgateway for batch jobs, and tune scrape intervals in kube-prometheus-stack.
Read ArticlePrometheus is the core time-series engine at the heart of kube-prometheus-stack, but the chart does not configure it directly — it uses the Prometheus Operator, which reads Kubernetes-native custom resources like ServiceMonitor, PodMonitor, and PrometheusRule to build Prometheus's scrape and alerting configuration automatically.
This category focuses on that layer specifically: how to monitor your own applications by defining ServiceMonitors, how PromQL queries work against the data Prometheus collects, and how the Operator pattern replaces manual prometheus.yml editing with declarative, GitOps-friendly Kubernetes objects.
Add additionalScrapeConfigs, wire up the Blackbox Exporter for uptime probes, run Pushgateway for batch jobs, and tune scrape intervals in kube-prometheus-stack.
Read ArticleLearn how to use Prometheus Operator ServiceMonitor and PodMonitor CRDs to monitor your own applications in Kubernetes. Step-by-step guide with YAML examples.
Read ArticleNot directly — the Prometheus Operator generates Prometheus's configuration from ServiceMonitor, PodMonitor, and PrometheusRule custom resources instead, though additionalScrapeConfigs is available as an escape hatch.
PromQL, Prometheus's own query language, which every Grafana dashboard and alert rule in kube-prometheus-stack is built on top of.