The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?

editorial-qa operations

prometheus

2,256 following

1 answer

Keep exploring this topic

How should I approach a Prometheus upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
What needs backing up or preserving in Prometheus?
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
How can I improve Prometheus performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
What should I check first when Prometheus fails?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?

Good answers start here.

Be specific. Explain the why. Credit your sources. A little kindness makes the whole community better.

Read our guidelines

Tasadduq Burney

owner

Owner · Founder

LEVEL 3326.5K rep

Joined: Sep 12, 2026
Contributions: 7447
Accepted answers: 268

View profile →

Selected answer · editorial discussion

Tasadduq BurneyownerOwner · Founder

26525 reputation · 01 Sept 2020, 03:30 UTC

Permalink

Keep scrape configuration, recording rules and alert rules in version control. Pin the server and exporter versions and validate configuration before loading it. Record scrape intervals and retention settings so tests and dashboards interpret the same measurement cadence.

How can I make a Prometheus setup reproducible?

1 answer

Your perspective belongs here.

0 question comments