You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps next to the road map, add a "non-road-map" with the non-goals, i.e. things that sound like nice features but which we do not intend to implement for reasons to be stated in the new section.
I personally wouldn't rule out retention policies (deleting certain series completely after a configurable time, not talking about downsampling here). It shouldn't be too hard to add and could be quite useful.
Thinking last night this is probably also the place to list our assumptions about the minimum state of your infrastructure (machine database, service database, configuration management), and that we won't add features solely to workaround the lack of same.
While I strongly disagree with the "no long-term storage" bit, a constraints section which lists design non-goals, anti-patterns, and basic requirements would make sense.
To clarify, the long-term storage part means we do not intend for the storage layer to become one. We do however intend to provide better integrations with existing storage solutions to serve as a LTS for Prometheus data. Compared to what we have now, this especially means read-back support.
Just to make sure: The plan is to put historic data into some other storage engine at a magic cut-off point to maintain performance for near-time metrics while retaining full information for old data?
Sounds good to me :)
As an aside, it might make sense to detect frequently-accessed historical data to keep that in warm storage.
As an aside, it might make sense to detect frequently-accessed historical data to keep that in warm storage.
I was thinking about a simple query cache here. Queries to the LTS backend only have to be repeated if the most recent sample (per timeseries) is now beyond the rentention period of the Prometheus server (or if the query result has been evicted from the cache due to memory constraints).
But note that there a lot of more urgent features to implement before we'll tackle read-back from LTS.
Using this comment to formalize the idea, as it seems to have evolved over the years:
Title: Non-Goals | Out of Scope Where it fits: In the roadmap as a separate section, or as a page in the same section (/docs/introduction/nongoals) What it includes: an updated, accurate, and relevant list of items from this issue, possibly formatted in a way like WHAT (the non-goal) and WHY 1-5 bullet points, possibly with a link/reference to a decision Who updates it: same party as the roadmap, maintainers, etc. How it stays updated: could be covered as part of your usual roadmap process
Activity
brian-brazil commentedon Aug 3, 2015
brian-brazil commentedon Aug 4, 2015
juliusv commentedon Aug 4, 2015
I personally wouldn't rule out retention policies (deleting certain series completely after a configurable time, not talking about downsampling here). It shouldn't be too hard to add and could be quite useful.
brian-brazil commentedon Aug 17, 2015
brian-brazil commentedon Aug 20, 2015
brian-brazil commentedon Oct 13, 2015
Thinking last night this is probably also the place to list our assumptions about the minimum state of your infrastructure (machine database, service database, configuration management), and that we won't add features solely to workaround the lack of same.
RichiH commentedon Jan 5, 2016
While I strongly disagree with the "no long-term storage" bit, a constraints section which lists design non-goals, anti-patterns, and basic requirements would make sense.
fabxc commentedon Jan 5, 2016
To clarify, the long-term storage part means we do not intend for the storage layer to become one. We do however intend to provide better integrations with existing storage solutions to serve as a LTS for Prometheus data. Compared to what we have now, this especially means read-back support.
RichiH commentedon Jan 5, 2016
Just to make sure: The plan is to put historic data into some other storage engine at a magic cut-off point to maintain performance for near-time metrics while retaining full information for old data?
Sounds good to me :)
As an aside, it might make sense to detect frequently-accessed historical data to keep that in warm storage.
beorn7 commentedon Jan 6, 2016
I was thinking about a simple query cache here. Queries to the LTS backend only have to be repeated if the most recent sample (per timeseries) is now beyond the rentention period of the Prometheus server (or if the query result has been evicted from the cache due to memory constraints).
But note that there a lot of more urgent features to implement before we'll tackle read-back from LTS.
brian-brazil commentedon Jun 2, 2016
brian-brazil commentedon Jul 6, 2016
brian-brazil commentedon Jul 7, 2016
juliusv commentedon Jul 7, 2016
2 remaining items
brian-brazil commentedon Jul 14, 2016
brian-brazil commentedon Aug 10, 2016
brian-brazil commentedon Dec 5, 2016
brian-brazil commentedon Mar 3, 2017
brian-brazil commentedon Aug 2, 2017
Reference non-goals in contributing guidelines
Reference non-goals in contributing guidelines (#4118)
Reference non-goals in contributing guidelines (prometheus#4118)
zgfh commentedon Jul 17, 2019
TLS and authentication in HTTP serving endpointsshould delete from roadmap docs (https://prometheus.io/docs/introduction/roadmap/)?beorn7 commentedon Jul 17, 2019
It's the other way round. The roadmap is more up to date than this.
Add PROXY Protocol support command line parameter document. (promethe…
jan--f commentedon Mar 18, 2026
Hello from the bug scrub!
Albeit this issue is older then Prometheus 2.0 this still seems like a good addition.
lasomethingsomething commentedon Nov 18, 2026
Using this comment to formalize the idea, as it seems to have evolved over the years:
Title: Non-Goals | Out of Scope
Where it fits: In the roadmap as a separate section, or as a page in the same section (
/docs/introduction/nongoals)What it includes: an updated, accurate, and relevant list of items from this issue, possibly formatted in a way like WHAT (the non-goal) and WHY 1-5 bullet points, possibly with a link/reference to a decision
Who updates it: same party as the roadmap, maintainers, etc.
How it stays updated: could be covered as part of your usual roadmap process