Skip to content
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

Simplify how experimental PromQL functions are enabled #10660

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

56quarters
Copy link
Contributor

@56quarters 56quarters commented Feb 14, 2025

What this PR does

Remove experimental configuration flags querier.promql-experimental-functions-enabled and query-frontend.block-promql-experimental-functions used for controlling access to experimental PromQL features. Instead enable experimental PromQL functions at the engine level by default, block access to them by default, and selectively enable them at a per-user level using the middleware introduced in #9798.

Justification for this change:

  • There are currently 3 different settings that need to changed to allow customers to make use experimental functions in PromQL that need to be applied 3 different places (queriers, query-frontend, and per-tenant limits).
  • The performance impact from always enabling but blocking via middleware experimental PromQL functions (what this PR does) is so small that it does not show up in profiling from what I can tell.

Which issue(s) this PR fixes or relates to

Related #9798

Checklist

  • Tests updated.
  • Documentation added.
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
  • about-versioning.md updated with experimental features.

Copy link
Contributor

github-actions bot commented Feb 14, 2025

Remove experimental configuration flags
`querier.promql-experimental-functions-enabled` and
`query-frontend.block-promql-experimental-functions` used for
controlling access to experimental PromQL features. Instead enable
experimental PromQL functions at the engine level by default, block
access to them by default, and selectively enable them at a per-user
level using the middleware introduced in #9798.

Justification for this change:
* There are currently 3 different settings that need to changed to
  allow customers to make use experimental functions in PromQL that
  need to be applied 3 differnt places (queriers, query-frontend, and
  per-tenant limits).
* The performance impact from always enabling but blocking via
  middleware experimental PromQL functions (what this PR does) is
  so small that it does not show up in profling from what I can
  tell.

Signed-off-by: Nick Pillitteri <[email protected]>
@56quarters 56quarters force-pushed the 56quarters/exp-config-cleanup branch from 7f8fad7 to 000554d Compare February 18, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant