Prometheus Guides for Kube-Prometheus-Stack

Prometheus 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.

Frequently Asked Questions

Does kube-prometheus-stack let me write raw Prometheus configuration files directly?

Not directly — the Prometheus Operator generates Prometheus's configuration from ServiceMonitor, PodMonitor, and PrometheusRule custom resources instead, though additionalScrapeConfigs is available as an escape hatch.

What query language does Prometheus use?

PromQL, Prometheus's own query language, which every Grafana dashboard and alert rule in kube-prometheus-stack is built on top of.