Preparing for a DevOps interview that covers Prometheus? These questions come up again and again - here are strong, concrete answers.
Q: What is Prometheus and why use it?
Prometheus scrapes metrics from HTTP endpoints, stores them as time series, and lets you query and alert on them with PromQL - the backbone of Kubernetes-era monitoring.
- Pull-based scraping with service discovery fits dynamic infrastructure
- PromQL makes rich, dimensional queries and alerts possible
- A huge ecosystem of exporters for almost everything
Q: What are the best practices you follow?
- 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
Q: What mistakes have you seen?
- High-cardinality labels (user IDs, request IDs) exploding memory
- Treating Prometheus as long-term storage without Thanos/Cortex
- Alerting on raw values instead of rates/ratios tied to user impact
Q: Show a basic configuration
Scrape config plus an alert rule.
# 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%" }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.