prometheus / prometheus/prometheus
Deltas: Design migration from d2c to native deltas
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 66.1k
- Forks
- 10.8k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 131
Description
Currently a lot of users are using the deltatocumulative processor to get their delta metrics into Prometheus. Theoretically, due to the design of native delta temporality support, these users should be able to remove that processor and have their metrics Just Work and maintain coherence in their metrics. But we need to test this, try it, and document it so we have a bulletproof HOWTO for doing this sort of migration. Is it as simple as disabling the processor? Or do we need more process to ensure everything works?
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 by reviewing the linked deltatocumulative processor and Prometheus's native delta temporality behavior. Test a migration that removes the processor and compare metric coherence before and after. Document the verified migration steps, including whether disabling the processor is sufficient and any additional process required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- documentation, observability
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100