Skip to content

Add non-goals #149

Open
Open

Description

@beorn7

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.

Ideas so far:

  • Rule templating language.
  • Strings as sample values (and neither ints...).
  • Support event logging / become a log db.

More?

Activity

  1. brian-brazil commented on Aug 3, 2015

    @brian-brazil
    Contributor
    • Supporting JSON as a scrape format
    • Long term storage in prometheus (hopefully)
    • Per-host aggregators
    • SSL and auth for our http frontends (use a reverse proxy)
  2. brian-brazil commented on Aug 4, 2015

    @brian-brazil
    Contributor
    • Retention policies/rollups (use remote storage for that)
  3. juliusv commented on Aug 4, 2015

    @juliusv
    Member

    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.

  4. brian-brazil commented on Aug 17, 2015

    @brian-brazil
    Contributor
    • Configurable logging (use a pipe)
  5. brian-brazil commented on Aug 20, 2015

    @brian-brazil
    Contributor
    • A single exporter per machines/service reporting in node exporter
  6. brian-brazil commented on Oct 13, 2015

    @brian-brazil
    Contributor

    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.

  7. RichiH commented on Jan 5, 2016

    @RichiH
    Member

    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.

  8. fabxc commented on Jan 5, 2016

    @fabxc
    Contributor

    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.

  9. RichiH commented on Jan 5, 2016

    @RichiH
    Member

    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.

  10. beorn7 commented on Jan 6, 2016

    @beorn7
    ContributorAuthor

    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.

  11. brian-brazil commented on Jun 2, 2016

    @brian-brazil
    Contributor
    • Non-HTTP scraping
  12. brian-brazil commented on Jul 6, 2016

    @brian-brazil
    Contributor
    • Metrics expiry/timeout in pushgateway
  13. brian-brazil commented on Jul 7, 2016

    @brian-brazil
    Contributor
    • Configuration being provided any way other than files on disk
  14. juliusv commented on Jul 7, 2016

    @juliusv
    Member
    • Anomaly detection (besides manually defined rules)
  15. 2 remaining items

  16. brian-brazil commented on Jul 14, 2016

    @brian-brazil
    Contributor
    • Anything to do with timezones (but local time as reported by your browser may be used in places)
  17. brian-brazil commented on Aug 10, 2016

    @brian-brazil
    Contributor
    • Anything that tracks/manages human responses to alerts (Use pagerduty&friends)
  18. brian-brazil commented on Dec 5, 2016

    @brian-brazil
    Contributor
    • Adding math to Prometheus console/alert templates (put it in the expression)
  19. brian-brazil commented on Mar 3, 2017

    @brian-brazil
    Contributor
    • Alertmanager permitting every single alert/resolution being turned into a notification (use alert stream from Prometheus directly)
  20. brian-brazil commented on Aug 2, 2017

    @brian-brazil
    Contributor
    • Non-standard and/or vendor specific authentication mechanisms for scraping
  21. zgfh commented on Jul 17, 2019

    @zgfh

    TLS and authentication in HTTP serving endpoints should delete from roadmap docs (https://prometheus.io/docs/introduction/roadmap/)?

  22. beorn7 commented on Jul 17, 2019

    @beorn7
    ContributorAuthor

    It's the other way round. The roadmap is more up to date than this.

  23. jan--f commented on Mar 18, 2026

    @jan--f
    Contributor

    Hello from the bug scrub!
    Albeit this issue is older then Prometheus 2.0 this still seems like a good addition.

  24. lasomethingsomething commented on Nov 18, 2026

    @lasomethingsomething

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions