Auto Downsampling Demystified (please) #6054
Unanswered
DanAyres
asked this question in
Questions & Answers
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear Thanos Maintainers,
I have read all the material I can find on the subject of downsampling
#601
#1170
#1353
https://thanos.io/tip/components/compact.md/#downsampling
(plus the usual google searching) and am still uncertain that the behaviour I observe is correct. My retention settings are as follows:
When using "Auto downsampling" in the Thanos UI and querying a time region that has only data downsampled to 5m (not running long enough for 1h yet) I do not get any results UNLESS I set the step to 1500 seconds. When using auto I would expect that ALL data within the time region I request are returned if they exist somewhere in the database.
If I make an API call to thanos query with "max_source_resolution": "5m" i.e.
data are returned at a resolution of 14 seconds. Why does "auto" not exhibit the same behaviour? The equivalent API call is:
Is there something I am misunderstanding about Auto downsampling? At the moment, with Grafana I have to explicitly set a min step of 1500 seconds in order to see data which is not ideal for my users and must be changed when I look at recent data.
This behaviour is observed on both
version 0.29.0
revision 194e1fa
and
version 0.30.1
revision 27e4714
I hope you can help.
Best wishes,
Dan
Beta Was this translation helpful? Give feedback.
All reactions