← All insightsProduction

Running Prometheus in production: a hardening checklist

CodeWizard Engineering · 28 May 2026 · 3 min read · Advanced

Demos and production are different sports. This checklist covers what changes when Prometheus has to be reliable, secure and observable under real load.

Security and reliability defaults

  • Put Prometheus behind auth/proxy; it has no built-in authentication
  • Scope exporters and avoid exposing internal metrics publicly

A production-minded config

Scrape config plus an alert rule.

yaml
# prometheus.yml
scrape_configs:
  - job_name: app
    static_configs: [{ targets: ['app:3000'] }]
---
# rules.yml
groups:
  - name: app
    rules:
      - alert: HighErrorRate
        expr: rate(http_requests_total{status=~"5.."}[5m]) > 0.05
        for: 10m
        labels: { severity: page }
        annotations: { summary: "5xx error rate above 5%" }

Operational best practices

  • Keep label cardinality low and stable
  • Alert on symptoms (latency, error ratio) via SLOs, not noisy causes
  • Use recording rules for expensive dashboards and remote-write for long-term storage
In production, boring and reproducible beats clever every time.

Want senior help putting Prometheus to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult