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
thanos, version 0.2.1 (branch: HEAD, revision: 30e7cbdafd3ef01189f202945c2728fcf37e1cf1)
build user: root@79ffcf51ff9b
build date: 20181227-15:44:56
go version: go1.11.4
prometheus, version 2.6.0 (branch: HEAD, revision: dbd1d58c894775c0788470944b818cc724f550fb)
build user: root@bf5760470f13
build date: 20181217-15:14:46
go version: go1.11.3
What happened
I recently did setup thanos for long term metric storage. After the first few weeks of running the setup, I tried to zoom out in grafana to see how everything works out. While zooming out to 30 days in grafana, I started to see gaps in the displayed metrics. There is metric data for the selected time range. If I do query prometheus directly, I get the expected results.
What you expected to happen
Getting all existing data when querying via thanos query.
@jojohappy you're right, I just built thanos from the master branch and the problem has gone away. I did miss the referenced bug, sorry for the duplication.
Thanos, Prometheus and Golang version used
What happened
I recently did setup thanos for long term metric storage. After the first few weeks of running the setup, I tried to zoom out in grafana to see how everything works out. While zooming out to 30 days in grafana, I started to see gaps in the displayed metrics. There is metric data for the selected time range. If I do query prometheus directly, I get the expected results.
What you expected to happen
Getting all existing data when querying via thanos query.
Full logs to relevant components
query.log
Queried via prometheus:
Queried via thanos query:
The text was updated successfully, but these errors were encountered: