-
Notifications
You must be signed in to change notification settings - Fork 544
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
Rewrite subqueries that have the same range and resolution #10445
Conversation
7019fd3
to
5c1f532
Compare
💻 Deploy preview deleted. |
5c1f532
to
92e3988
Compare
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.
LGTM. Thanks for doing this!
Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed).
44d09d5
to
7c4e255
Compare
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.
lgtm for the rewrites we want to do
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-10445-to-r325 origin/r325
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b812677266850268b4b00dd689a3baedb13a87b2
# Push it to GitHub
git push --set-upstream origin backport-10445-to-r325
git switch main
# Remove the local backport branch
git branch -D backport-10445-to-r325 Then, create a pull request where the |
* Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
…10459) * Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
From feedback #10459 (comment) Related #10445 Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
* Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
…10463) * Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
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.
Two small suggestions:
* docs: Fix help text for query-frontend.prom2-range-compat flag From feedback #10459 (comment) Related #10445 Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
* Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
…10472) * Rewrite subqueries that have the same range and resolution Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed). * Changelog Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> (cherry picked from commit b812677)
Follow up to #10445, add a metric when queries are rewritten for compatibility with Prometheus 3 range selector semantics. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
Follow up to #10445, add a metric when queries are rewritten for compatibility with Prometheus 3 range selector semantics. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
* Add visibility when subqueries are rewritten Follow up to #10445, add a metric when queries are rewritten for compatibility with Prometheus 3 range selector semantics. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> * Skip TestSampleTracker_Concurrency since it is not reliable Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com> --------- Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
What this PR does
Fix queries that have the same range and resolution since this will only return a single point when using Prometheus 3 selectors, left open and right closed (compared to Prometheus 2 left closed and right closed).
Which issue(s) this PR fixes or relates to
Internal incident
Notes for reviewers
These names were the first things I thought of, please feel free to suggest better ones!
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.