Thanos, Prometheus and Golang version used
thanos, version 0.3.2 (branch: master, revision: 8e53a42515c591bb5fb58fa38d795f146704034d)
build user: root@packages-build-f2e9be33-d451-4201-a013-97a6f0686e26-l995n
build date: 20190430-09:03:56
go version: go1.10.1
This is a custom version, patched with #1094
Prometheus 2.9.2
What happened
We've configured the compactor to keep raw data for 14 days and delete it afterwards, and the query component to auto-downsample data. For queries that span over a week the results look like the ones we expected when compared with another setup in which we have kept raw data. Now, when the query window is smaller than 105h we are not getting any results back, unless we specifically force it in the UI to use 5m downsampled.
What you expected to happen
That the data that does exist would be returned, even though it has a lower resolution.
How to reproduce it (as minimally and precisely as possible):
- Duplicate a bucket.
- Compact the new bucket with a configuration that removes raw data after 14 days and keeps the rest.
- Have another environment use the new bucket.
- Query both environments to see the difference.
Full logs to relevant components
The logs don't show anything odd, at least with the info level. I'm going to restart the store with debug and will add whatever is interesting here, if there's anything.
Anything else we need to know
Nothing I can think of right now.
Thanos, Prometheus and Golang version used
This is a custom version, patched with #1094
Prometheus 2.9.2
What happened
We've configured the compactor to keep raw data for 14 days and delete it afterwards, and the query component to auto-downsample data. For queries that span over a week the results look like the ones we expected when compared with another setup in which we have kept raw data. Now, when the query window is smaller than 105h we are not getting any results back, unless we specifically force it in the UI to use 5m downsampled.
What you expected to happen
That the data that does exist would be returned, even though it has a lower resolution.
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components
The logs don't show anything odd, at least with the
infolevel. I'm going to restart the store withdebugand will add whatever is interesting here, if there's anything.Anything else we need to know
Nothing I can think of right now.