-
Notifications
You must be signed in to change notification settings - Fork 804
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
Time check in query priority now considers overall data select time window (including range selectors, modifiers and lookback delta) #5758
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
justinjung04
changed the title
Improve time bound check for query priority
Time range of subqueries are now considered when determining query priority
Jan 30, 2024
Signed-off-by: Justin Jung <jungjust@amazon.com>
Signed-off-by: Justin Jung <jungjust@amazon.com>
justinjung04
force-pushed
the
query-priority
branch
from
January 30, 2024 23:18
8a5699a
to
f47fc78
Compare
Signed-off-by: Justin Jung <jungjust@amazon.com>
yeya24
reviewed
Jan 31, 2024
justinjung04
changed the title
Time range of subqueries are now considered when determining query priority
Time check in query priority now considers offsets, @ modifiers and range selectors.
Feb 1, 2024
justinjung04
changed the title
Time check in query priority now considers offsets, @ modifiers and range selectors.
Time check in query priority now considers range selectors, modifiers and lookback delta.
Feb 1, 2024
Signed-off-by: Justin Jung <jungjust@amazon.com>
Signed-off-by: Justin Jung <jungjust@amazon.com>
yeya24
reviewed
Feb 2, 2024
Signed-off-by: Justin Jung <jungjust@amazon.com>
Signed-off-by: Justin Jung <jungjust@amazon.com>
justinjung04
changed the title
Time check in query priority now considers range selectors, modifiers and lookback delta.
Time check in query priority now considers overall data fetched time window (including range selectors, modifiers and lookback delta)
Feb 2, 2024
Signed-off-by: Justin Jung <jungjust@amazon.com>
justinjung04
changed the title
Time check in query priority now considers overall data fetched time window (including range selectors, modifiers and lookback delta)
Time check in query priority now considers overall data select time window (including range selectors, modifiers and lookback delta)
Feb 5, 2024
Signed-off-by: Justin Jung <jungjust@amazon.com>
justinjung04
force-pushed
the
query-priority
branch
from
February 5, 2024 19:56
5690fdb
to
887f111
Compare
Signed-off-by: Justin Jung <jungjust@amazon.com>
yeya24
approved these changes
Feb 6, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @justinjung04! Thanks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
Improves time bound check for query priority, such that the range of subquery is also evaluated.
Also, added
data_fetch_min_time
anddata_fetch_max_time
in query stats to help with query priority configuration.For example,
ts=2024-02-05T22:08:44.07399Z caller=handler.go:372 level=info org_id=fake msg="query stats" component=query-frontend method=POST path=/prometheus/api/v1/query_range response_time=3.655097ms query_wall_time_seconds=0.002303539 fetched_series_count=1 fetched_chunks_count=1 fetched_samples_count=6 fetched_chunks_bytes=38 fetched_data_bytes=212 split_queries=1 status_code=200 response_size=357 data_select_max_time=1707170910 data_select_min_time=1707163710 query_length=2 user_agent=Grafana/9.4.3 priority=2 param_start=1707167310 param_step=15 param_end=1707170910 param_query=up
Which issue(s) this PR fixes:
n/a
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]