Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High retention on Prometheus #283

Closed
metalmatze opened this issue Apr 12, 2018 · 3 comments
Closed

High retention on Prometheus #283

metalmatze opened this issue Apr 12, 2018 · 3 comments
Labels

Comments

@metalmatze
Copy link
Contributor

metalmatze commented Apr 12, 2018

In the example the retention for Prometheus itself is set to 24h.
When setting this to, for example, 1 week (168h) does Thanos query the object storage less for that time range?

@bwplotka
Copy link
Member

bwplotka commented Apr 12, 2018

Hello!
Good question. (:

TL;DR: No. For Thanos query it does not matter if the underlying Store API is store, sidecar or ruler.

This is related discussion: #82 I remember I started doing some implementation of it, but essentially this is bit fuzzy problem and not straightforward, so we aborted. Basically:

  • you don't know how many stores you have in the system. We aimed to support one per bucket for now, but you can have multiple buckets.
  • you don't really know what "sources" (what metrics) store node has access too.
  • races can happen (although that could be mitigated by some time margin).
  • we are not really sure if it's "better" to ask store or Prometheus (sidecar/source). Better means cheaper? faster? simpler? more resilient?

@bwplotka
Copy link
Member

@metalmatze does it answer your question? Can we close this?

@metalmatze
Copy link
Contributor Author

Yes. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants