prometheus / prometheus/prometheus
promtool: Add ability to "dump" whole blocks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 66.1k
- Forks
- 10.8k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 131
Description
Proposal
We can dump data from Prometheus with promtool tsdb dump, but unfortunately we can only import it back in OpenMetrics format so we can't re-use this file to import that data into another Prometheus server. The proposal is to add support for creating Prometheus compatible blocks from the same format that we currently dump, so we can move data from different prometheus easily.
Use case. Why is this important?
Where I work, a decision was made in the past that we'd have one Prometheus server for each application/exporter and it's not scaling too well. We'd like to consolidate all that data into a single Prometheus that will now scrape all our metrics endpoints. We want to shut down several Prometheus, but we'd like to keep their data in our new centralized one.
With this proposal, it will be a lot easier to dump and import data from one prometheus instance to another.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the promtool tsdb dump entry point and trace how its output is imported through OpenMetrics. Define how that dump format can produce Prometheus-compatible blocks for another server. Done means data can be dumped from one Prometheus instance and imported into another without requiring OpenMetrics conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100