-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
query: Misleading message when there are no metrics during the announced timerange of a store #4478
Comments
@amine250 that indeed sounds like a bug in query - help wanted. |
I did some digging into this and the issue is the fronted gets the min max time it shows from this InfoResponse returned by store thanos/pkg/store/storepb/rpc.pb.go Line 224 in 360b39e
which is set to:
in this function Line 640 in 8184ba2
when no data is available in the bucket during the specified --min-time and --max-time .So the solution could be pass values of those args as part of the InfoResponse? WDYT @ianbillett ? |
To me, this info was always supposed to be the actually expected time range of ANY data from this component. This means that we probably should add that as comment to storeAPI protocol too. To describe it, let's show following examples:
|
Anyway, this issue is valid. IMO Action Items:
|
Hello 👋 Looks like there was no activity on this issue for the last two months. |
Closing for now as promised, let us know if you need this to be reopened! 🤗 |
This has been addressed in #4908 as well |
Thanos, Prometheus and Golang version used:
Object Storage Provider:
AWS S3
What happened:
Wanting to time shard the store component, I've configured
--max-time=-7d
and--min-time=-30d
in one of the stores. No metrics have been scraped during this timerange.While the date and the timerange are valid, the querier show that the max time is invalid.
What you expected to happen:
Show the Max Time that has been configured in the command line.
How to reproduce it (as minimally and precisely as possible):
--max-time
and--min-time
during which there are no metrics in the object storage.--store
to this newly created store componentFull logs to relevant components:
The text was updated successfully, but these errors were encountered: