Duration expression: Rename min/max -> min_of, max_of by roidelapluie · Pull Request #18687 · prometheus/prometheus

roidelapluie · 2026-05-13T15:52:07Z

This PR makes two related changes to PromQL:

Rename the min() and max() duration-expression functions (introduced under the experimental-duration-expr feature flag) to min_of() and max_of().
Add min_of(a, b) and max_of(b, b) as first-class scalar-returning experimental PromQL functions.

The names min and max are already taken by well-known PromQL aggregate operators. Keeping them as duration-expression keywords would create ambiguity — the parser would need to disambiguate based on context, and users would be surprised by the overlap.

The new min_of(a, b) / max_of(a, b) scalar functions operate on two scalar arguments and return the smaller or larger value respectively (backed by math.Min / math.Max). They are available under the promql-experimental-functions feature flag.

Which issue(s) does the PR fix:

Release notes for end users (ALL commits must be considered).

Reviewers should verify clarity and quality.

[FEATURE] PromQL: Add `min_of(a, b)` and `max_of(a, b)` scalar experimental functions, returning the smaller or larger of two scalar values.
[CHANGE] PromQL: Rename the `min()` and `max()` duration-expression functions (experimental feature flag `experimental-duration-expr`) to `min_of()` and `max_of()` to avoid confusion with the `min` and `max` aggregate operators.

Rename the `min()` and `max()` duration expression functions to `least()` and `greatest()` to avoid conflicts with the existing PromQL aggregate functions `min` and `max`. Update documentation and tests accordingly. Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>

Implement least(a, b) and greatest(a, b) as scalar-returning PromQL functions backed by math.Min and math.Max respectively. Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>

krajorama · 2026-05-19T07:32:31Z

I don't quite get the motivation for this. Looking at the tests, min/max are much easier to read. Also, isn't figuring out the intended use from the context already implemented? What is the example that is causing confusion? Did we get feedback from somebody ?

roidelapluie · 2026-05-19T08:37:27Z

I don't quite get the motivation for this. Looking at the tests, min/max are much easier to read. Also, isn't figuring out the intended use from the context already implemented? What is the example that is causing confusion? Did we get feedback from somebody ?

Here is the concern: foo[max(1m, 2m)] is valid, while predict_linear(foo[1h], max(1m, 2m)) is not. Although technically consistent, this requires understanding that max() can mean either numeric comparison or vector aggregation depending on context, which may not be obvious to users.
Using distinct names such as least / greatest (following SQL conventions), or alternatives like max_of() / scalar_max(), would make the distinction clearer and avoid overloading the existing aggregator names.

krajorama · 2026-05-19T08:57:23Z

Here is the concern: foo[max(1m, 2m)] is valid, while predict_linear(foo[1h], max(1m, 2m)) is not. Although technically consistent, this requires understanding that max() can mean either numeric comparison or vector aggregation depending on context, which may not be obvious to users. Using distinct names such as least / greatest (following SQL conventions), or alternatives like max_of() / scalar_max(), would make the distinction clearer and avoid overloading the existing aggregator names.

I see. I've checked the docs (+Claude) and we don't have polymorphism in any aggregation operator/function currently. Math operators like +,-,etc do support it.

We already have variants to some degree as in : min(instant-vector) vs min_over_time(range-vector). So I think min_scalars(scalars...) or min_of(scalars...) would be best in line with what we have.

It's a matter of taste a little bit, so would be nice to get more input cc @juliusv I'll ask today in the bug scrub.

roidelapluie · 2026-05-19T09:55:04Z

I added a second commit that renames to min_of, max_of.

Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>

krajorama · 2026-05-20T08:07:09Z

Here is the concern: foo[max(1m, 2m)] is valid, while predict_linear(foo[1h], max(1m, 2m)) is not. Although technically consistent, this requires understanding that max() can mean either numeric comparison or vector aggregation depending on context, which may not be obvious to users. Using distinct names such as least / greatest (following SQL conventions), or alternatives like max_of() / scalar_max(), would make the distinction clearer and avoid overloading the existing aggregator names.

I see. I've checked the docs (+Claude) and we don't have polymorphism in any aggregation operator/function currently. Math operators like +,-,etc do support it.

We already have variants to some degree as in : min(instant-vector) vs min_over_time(range-vector). So I think min_scalars(scalars...) or min_of(scalars...) would be best in line with what we have.

It's a matter of taste a little bit, so would be nice to get more input cc @juliusv I'll ask today in the bug scrub.

The bug scrub didn't have @bboreham or @bwplotka . @ldufr and me would be ok with min_of, max_of.

juliusv · 2026-05-20T09:32:51Z

Yeah, I was actually the one pinging @roidelapluie originally about that ambiguity, which I think would be bad to keep. And it's not just the same type of overloading as we have with arithmetic operators, since the operation being done is more different than in those (aggregation over dimensions within a parameter vs. picking one of a list of supplied scalar arguments).

So either least / greatest or min_of / max_of would be fine with me.

juliusv

👍

(though curious what made you go with min_of / max_of over the more SQL-ish variants in the end)

krajorama · 2026-05-21T08:27:25Z

👍

(though curious what made you go with min_of / max_of over the more SQL-ish variants in the end)

I suggested it, since we already have that kind of variation , see: min vs min_over_time. And last time I used SQL was 20 years ago so it just looked weird to me.

roidelapluie · 2026-05-21T08:34:36Z

Thanks!

bwplotka

Makes sense, thanks!

This change adds an implementation of the experimental PromQL functions `min_of` and `max_of` introduced in prometheus/prometheus#18687.

This change adds an implementation of the experimental PromQL functions `min_of` and `max_of` introduced in prometheus/prometheus#18687. Fixes #15596

…➔ v3.13.0) (#1360) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [quay.io/prometheus/prometheus](https://github.com/prometheus/prometheus) | minor | `v3.12.0` → `v3.13.0` | --- ### Release Notes <details> <summary>prometheus/prometheus (quay.io/prometheus/prometheus)</summary> ### [`v3.13.0`](https://github.com/prometheus/prometheus/releases/tag/v3.13.0): 3.13.0 / 2026-07-01 [Compare Source](prometheus/prometheus@v3.12.0...v3.13.0) This is a Long Term Support [LTS](https://prometheus.io/docs/introduction/release-cycle/) release. - \[SECURITY] UI: Bump `sanitize-html` to fix a cross-site scripting vulnerability (CVE-2026-44990). [#18697](prometheus/prometheus#18697) - \[CHANGE] UI: Third-party npm dependency licenses are now embedded in the Prometheus binary and served at `/assets/third-party-licenses.txt`, replacing the `npm_licenses.tar.bz2` archive previously shipped in release tarballs and container images. [#18997](prometheus/prometheus#18997) - \[CHANGE] API: Use SHA-256 instead of SHA-1 to generate rule group pagination tokens. [#18927](prometheus/prometheus#18927) - \[CHANGE] HTTP clients: Credentials (Authorization header, basic auth, bearer token, OAuth2, configured headers) are no longer forwarded when following a redirect to a different host; affects scraping, remote read/write, alerting, and service discovery. Via prometheus/common v0.69.0 (CVE-2025-4673 CVE-2023-45289). [#18949](prometheus/prometheus#18949) - \[CHANGE] promtool: Relative file paths in the file passed to `--http.config.file` are now resolved relative to that config file's directory instead of its parent directory. Via prometheus/common v0.69.0. [#18949](prometheus/prometheus#18949) - \[CHANGE] PromQL: Rename the `min()` and `max()` duration-expression functions (experimental feature flag `experimental-duration-expr`) to `min_of()` and `max_of()` to avoid confusion with the `min` and `max` aggregate operators. [#18687](prometheus/prometheus#18687) - \[FEATURE] API: Add experimental search endpoints to search metric names, label names, and label values. [#18573](prometheus/prometheus#18573) - \[FEATURE] Discovery/AWS: Add ability to filter RDS instances. [#18859](prometheus/prometheus#18859) - \[FEATURE] PromQL: Add `min_of(a, b)` and `max_of(a, b)` scalar experimental functions, returning the smaller or larger of two scalar values. [#18687](prometheus/prometheus#18687) - \[FEATURE] PromQL: Add support for smoothed/anchored rate with native histograms. [#18564](prometheus/prometheus#18564) - \[FEATURE] PromQL: Expose per-query `samplesRead` (and `samplesReadPerStep` with `stats=all` and the `promql-per-step-stats` feature flag) in the query stats response, and add the `prometheus_engine_query_samples_read_total` engine counter. `samplesRead` reflects storage I/O distinct from `totalQueryableSamples`, which counts samples loaded into the evaluator (and so over-counts when a sample is reused across multiple range-vector windows). [#18081](prometheus/prometheus#18081) - \[FEATURE] Scrape: Add `__convert_classic_histograms_to_nhcb__` internal label to allow per-target override of `convert_classic_histograms_to_nhcb` scrape configuration via relabeling. [#18840](prometheus/prometheus#18840) - \[FEATURE] TSDB: Add `storage.tsdb.chunk_encoding.floats` configuration field to select float chunk encoding (`xor` or `xor2`) at runtime, independently of the `--enable-feature=xor2-encoding` flag. [#18769](prometheus/prometheus#18769) - \[FEATURE] remote\_write: Add Certificate support for ingesting data into an Azure Monitor Workspace. [#18217](prometheus/prometheus#18217) - \[FEATURE] Scrape: Add `__always_scrape_classic_histograms__` and `__scrape_native_histograms__` internal labels to allow per-target override of the `always_scrape_classic_histograms` and `scrape_native_histograms` scrape configuration via relabeling. [#18929](prometheus/prometheus#18929) - \[ENHANCEMENT] Release: Container images are now also published to the GitHub Container Registry (ghcr.io). [#18791](prometheus/prometheus#18791) - \[ENHANCEMENT] PromQL: Prettify `fill_left(x) fill_right(x)` as `fill(x)` when both fill values are equal. [#18851](prometheus/prometheus#18851) - \[ENHANCEMENT] UI: Improve autocompletion after closing a function bracket. [#18894](prometheus/prometheus#18894) - \[PERF] Labels: Add case-insensitive prefix matching to speed up evaluation of long case-insensitive regular expressions (up to \~2x faster). [#18540](prometheus/prometheus#18540) - \[PERF] TSDB: Reduce per-sample overhead in chunk population, speeding up affected queries by \~12-15% in benchmarks. [#18699](prometheus/prometheus#18699) - \[PERF] TSDB: Eliminate unnecessary heap allocations in the V2 histogram WAL decoder, reducing allocations by up to 50% and memory by up to 10% for deployments using native histograms with created-timestamp storage enabled (`--enable-feature=created-timestamp-zero-ingestion`). [#18813](prometheus/prometheus#18813) - \[BUGFIX] Discovery/AWS: Fix failure when processing an AWS RDS cluster without instances. [#18845](prometheus/prometheus#18845) - \[BUGFIX] Fix race condition in initTime that could cause ErrOutOfBounds. [#18629](prometheus/prometheus#18629) - \[BUGFIX] PromQL: A range query whose `end` was not aligned to `step` caused subqueries inside it to evaluate past the parent's last actual step, inflating `peakSamples` in the query stats and against the `query.max-samples` limit, and wasting storage I/O reading samples that were never used in the result. [#18081](prometheus/prometheus#18081) - \[BUGFIX] PromQL: A range query containing an at-modifier-unsafe function over a range-vector with an `@` modifier (e.g. `predict_linear(metric[60s] @ T, X)`) silently under-counted `totalQueryableSamples` for steps after step 0. [#18081](prometheus/prometheus#18081) - \[BUGFIX] PromQL: Fix `fill_left`/`fill_right` producing missing samples in range queries when using `group_left`/`group_right`. [#18850](prometheus/prometheus#18850) - \[BUGFIX] PromQL: Fix for resets() and changes() in anchored range extenders with histograms. [#18906](prometheus/prometheus#18906) - \[BUGFIX] PromQL: Fix panic on `1[5m] smoothed` and similar expressions when extended range selectors are enabled. [#18764](prometheus/prometheus#18764) - \[BUGFIX] PromQL: Fix panic when a `smoothed` instant vector selector produces no samples for a series. [#18943](prometheus/prometheus#18943) - \[BUGFIX] PromQL: Fix panic when using a parenthesised plain number as an offset (e.g. `foo offset -(5)`). [#18768](prometheus/prometheus#18768) - \[BUGFIX] promtool: Fix panic when parsing exposition text containing empty braces `{}`. Via prometheus/common v0.69.0. [#18949](prometheus/prometheus#18949) - \[BUGFIX] Promtool: Fix `check healthy` and `check ready` when `--url` ends with a trailing slash. [#18854](prometheus/prometheus#18854) - \[BUGFIX] Rules: Close PromQL query after each rule evaluation to ensure resources are released. [#18733](prometheus/prometheus#18733) - \[BUGFIX] Scaleway SD: Resolve VPC/IPAM-only instances that have no legacy `private_ip` or `public_ip` field, but do have private NICs attached. [#18772](prometheus/prometheus#18772) - \[BUGFIX] TSDB: Do not leak head series when an integer histogram append is rejected (e.g. out-of-order). [#18838](prometheus/prometheus#18838) - \[BUGFIX] UI: Escape label values offered by PromQL autocomplete. [#18658](prometheus/prometheus#18658) - \[BUGFIX] TSDB: Fix chunk snapshot encoding for EncXOR2 chunks, preventing corruption on TSDB restart when EncXOR2-encoded series were present. [#18739](prometheus/prometheus#18739) - \[BUGFIX] TSDB: Store a millisecond timestamp (not a WAL segment number) in walExpiries when a series is evicted via CompactStaleHead/CompactSelectedSeries, so the series's label record is correctly retained in the next WAL checkpoint and replays cleanly. [#18847](prometheus/prometheus#18847) - \[BUGFIX] TSDB: Prevent loss of samples at the chunk-range boundary when CompactSelectedSeries (and CompactStaleHead) evict the series — the per-slice compaction loop now runs one more iteration so the boundary timestamp is captured in a block before the in-memory copy is removed. [#18849](prometheus/prometheus#18849) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://git.erwanleboucher.dev/eleboucher/homelab/pulls/1360

##### [\`v3.13.0\`](https://github.com/prometheus/prometheus/releases/tag/v3.13.0) This is a Long Term Support [LTS](https://prometheus.io/docs/introduction/release-cycle/) release. - \[SECURITY] UI: Bump `sanitize-html` to fix a cross-site scripting vulnerability (CVE-2026-44990). [#18697](prometheus/prometheus#18697) - \[CHANGE] UI: Third-party npm dependency licenses are now embedded in the Prometheus binary and served at `/assets/third-party-licenses.txt`, replacing the `npm_licenses.tar.bz2` archive previously shipped in release tarballs and container images. [#18997](prometheus/prometheus#18997) - \[CHANGE] API: Use SHA-256 instead of SHA-1 to generate rule group pagination tokens. [#18927](prometheus/prometheus#18927) - \[CHANGE] HTTP clients: Credentials (Authorization header, basic auth, bearer token, OAuth2, configured headers) are no longer forwarded when following a redirect to a different host; affects scraping, remote read/write, alerting, and service discovery. Via prometheus/common v0.69.0 (CVE-2025-4673 CVE-2023-45289). [#18949](prometheus/prometheus#18949) - \[CHANGE] promtool: Relative file paths in the file passed to `--http.config.file` are now resolved relative to that config file's directory instead of its parent directory. Via prometheus/common v0.69.0. [#18949](prometheus/prometheus#18949) - \[CHANGE] PromQL: Rename the `min()` and `max()` duration-expression functions (experimental feature flag `experimental-duration-expr`) to `min_of()` and `max_of()` to avoid confusion with the `min` and `max` aggregate operators. [#18687](prometheus/prometheus#18687) - \[FEATURE] API: Add experimental search endpoints to search metric names, label names, and label values. [#18573](prometheus/prometheus#18573) - \[FEATURE] Discovery/AWS: Add ability to filter RDS instances. [#18859](prometheus/prometheus#18859) - \[FEATURE] PromQL: Add `min_of(a, b)` and `max_of(a, b)` scalar experimental functions, returning the smaller or larger of two scalar values. [#18687](prometheus/prometheus#18687) - \[FEATURE] PromQL: Add support for smoothed/anchored rate with native histograms. [#18564](prometheus/prometheus#18564) - \[FEATURE] PromQL: Expose per-query `samplesRead` (and `samplesReadPerStep` with `stats=all` and the `promql-per-step-stats` feature flag) in the query stats response, and add the `prometheus_engine_query_samples_read_total` engine counter. `samplesRead` reflects storage I/O distinct from `totalQueryableSamples`, which counts samples loaded into the evaluator (and so over-counts when a sample is reused across multiple range-vector windows). [#18081](prometheus/prometheus#18081) - \[FEATURE] Scrape: Add `__convert_classic_histograms_to_nhcb__` internal label to allow per-target override of `convert_classic_histograms_to_nhcb` scrape configuration via relabeling. [#18840](prometheus/prometheus#18840) - \[FEATURE] TSDB: Add `storage.tsdb.chunk_encoding.floats` configuration field to select float chunk encoding (`xor` or `xor2`) at runtime, independently of the `--enable-feature=xor2-encoding` flag. [#18769](prometheus/prometheus#18769) - \[FEATURE] remote\_write: Add Certificate support for ingesting data into an Azure Monitor Workspace. [#18217](prometheus/prometheus#18217) - \[FEATURE] Scrape: Add `__always_scrape_classic_histograms__` and `__scrape_native_histograms__` internal labels to allow per-target override of the `always_scrape_classic_histograms` and `scrape_native_histograms` scrape configuration via relabeling. [#18929](prometheus/prometheus#18929) - \[ENHANCEMENT] Release: Container images are now also published to the GitHub Container Registry (ghcr.io). [#18791](prometheus/prometheus#18791) - \[ENHANCEMENT] PromQL: Prettify `fill_left(x) fill_right(x)` as `fill(x)` when both fill values are equal. [#18851](prometheus/prometheus#18851) - \[ENHANCEMENT] UI: Improve autocompletion after closing a function bracket. [#18894](prometheus/prometheus#18894) - \[PERF] Labels: Add case-insensitive prefix matching to speed up evaluation of long case-insensitive regular expressions (up to \~2x faster). [#18540](prometheus/prometheus#18540) - \[PERF] TSDB: Reduce per-sample overhead in chunk population, speeding up affected queries by \~12-15% in benchmarks. [#18699](prometheus/prometheus#18699) - \[PERF] TSDB: Eliminate unnecessary heap allocations in the V2 histogram WAL decoder, reducing allocations by up to 50% and memory by up to 10% for deployments using native histograms with created-timestamp storage enabled (`--enable-feature=created-timestamp-zero-ingestion`). [#18813](prometheus/prometheus#18813) - \[BUGFIX] Discovery/AWS: Fix failure when processing an AWS RDS cluster without instances. [#18845](prometheus/prometheus#18845) - \[BUGFIX] Fix race condition in initTime that could cause ErrOutOfBounds. [#18629](prometheus/prometheus#18629) - \[BUGFIX] PromQL: A range query whose `end` was not aligned to `step` caused subqueries inside it to evaluate past the parent's last actual step, inflating `peakSamples` in the query stats and against the `query.max-samples` limit, and wasting storage I/O reading samples that were never used in the result. [#18081](prometheus/prometheus#18081) - \[BUGFIX] PromQL: A range query containing an at-modifier-unsafe function over a range-vector with an `@` modifier (e.g. `predict_linear(metric[60s] @ T, X)`) silently under-counted `totalQueryableSamples` for steps after step 0. [#18081](prometheus/prometheus#18081) - \[BUGFIX] PromQL: Fix `fill_left`/`fill_right` producing missing samples in range queries when using `group_left`/`group_right`. [#18850](prometheus/prometheus#18850) - \[BUGFIX] PromQL: Fix for resets() and changes() in anchored range extenders with histograms. [#18906](prometheus/prometheus#18906) - \[BUGFIX] PromQL: Fix panic on `1[5m] smoothed` and similar expressions when extended range selectors are enabled. [#18764](prometheus/prometheus#18764) - \[BUGFIX] PromQL: Fix panic when a `smoothed` instant vector selector produces no samples for a series. [#18943](prometheus/prometheus#18943) - \[BUGFIX] PromQL: Fix panic when using a parenthesised plain number as an offset (e.g. `foo offset -(5)`). [#18768](prometheus/prometheus#18768) - \[BUGFIX] promtool: Fix panic when parsing exposition text containing empty braces `{}`. Via prometheus/common v0.69.0. [#18949](prometheus/prometheus#18949) - \[BUGFIX] Promtool: Fix `check healthy` and `check ready` when `--url` ends with a trailing slash. [#18854](prometheus/prometheus#18854) - \[BUGFIX] Rules: Close PromQL query after each rule evaluation to ensure resources are released. [#18733](prometheus/prometheus#18733) - \[BUGFIX] Scaleway SD: Resolve VPC/IPAM-only instances that have no legacy `private_ip` or `public_ip` field, but do have private NICs attached. [#18772](prometheus/prometheus#18772) - \[BUGFIX] TSDB: Do not leak head series when an integer histogram append is rejected (e.g. out-of-order). [#18838](prometheus/prometheus#18838) - \[BUGFIX] UI: Escape label values offered by PromQL autocomplete. [#18658](prometheus/prometheus#18658) - \[BUGFIX] TSDB: Fix chunk snapshot encoding for EncXOR2 chunks, preventing corruption on TSDB restart when EncXOR2-encoded series were present. [#18739](prometheus/prometheus#18739) - \[BUGFIX] TSDB: Store a millisecond timestamp (not a WAL segment number) in walExpiries when a series is evicted via CompactStaleHead/CompactSelectedSeries, so the series's label record is correctly retained in the next WAL checkpoint and replays cleanly. [#18847](prometheus/prometheus#18847) - \[BUGFIX] TSDB: Prevent loss of samples at the chunk-range boundary when CompactSelectedSeries (and CompactStaleHead) evict the series — the per-slice compaction loop now runs one more iteration so the boundary timestamp is captured in a block before the in-memory copy is removed. [#18849](prometheus/prometheus#18849)

roidelapluie requested a review from a team as a code owner May 13, 2026 15:52

roidelapluie requested a review from juliusv May 13, 2026 15:52

roidelapluie force-pushed the roidelapluie/greatest_least branch 2 times, most recently from edccf6c to 5b1a1c4 Compare May 18, 2026 08:50

promql: add least() and greatest() scalar functions

7af21f1

Implement least(a, b) and greatest(a, b) as scalar-returning PromQL functions backed by math.Min and math.Max respectively. Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>

roidelapluie force-pushed the roidelapluie/greatest_least branch from 5b1a1c4 to 7af21f1 Compare May 18, 2026 09:15

krajorama self-requested a review May 19, 2026 07:24

roidelapluie force-pushed the roidelapluie/greatest_least branch from 91f94b6 to 3b85104 Compare May 19, 2026 09:49

roidelapluie changed the title ~~Duration expression: Rename min/max -> least/greatest~~ Duration expression: Rename min/max -> min_of, max_of May 19, 2026

PromQL: Rename greatest, least, to max_of, min_of.

a74f0b2

Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>

roidelapluie force-pushed the roidelapluie/greatest_least branch from 3b85104 to a74f0b2 Compare May 19, 2026 11:07

juliusv approved these changes May 20, 2026

View reviewed changes

roidelapluie merged commit aa260fc into prometheus:main May 21, 2026
35 checks passed

bwplotka reviewed May 25, 2026

View reviewed changes

56quarters mentioned this pull request Jun 8, 2026

promql: Add range query tests for experimental max_of/min_of #18888

Closed

56quarters added a commit to grafana/mimir that referenced this pull request Jun 8, 2026

MQE: Add support for experimental min_of/max_of functions

f409d36

This change adds an implementation of the experimental PromQL functions `min_of` and `max_of` introduced in prometheus/prometheus#18687.

56quarters mentioned this pull request Jun 8, 2026

MQE: Add support for experimental min_of/max_of functions grafana/mimir#15597

Merged

4 tasks

56quarters added a commit to grafana/mimir that referenced this pull request Jun 9, 2026

MQE: Add support for experimental min_of/max_of functions

0638934

This change adds an implementation of the experimental PromQL functions `min_of` and `max_of` introduced in prometheus/prometheus#18687.

krajorama mentioned this pull request Jun 18, 2026

chore: prepare 3.13.0-rc.0 release #18965

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Duration expression: Rename min/max -> min_of, max_of#18687

Duration expression: Rename min/max -> min_of, max_of#18687
roidelapluie merged 3 commits into
prometheus:mainfrom
roidelapluie:roidelapluie/greatest_least

roidelapluie commented May 13, 2026 •

edited

Loading

Uh oh!

krajorama commented May 19, 2026

Uh oh!

roidelapluie commented May 19, 2026

Uh oh!

krajorama commented May 19, 2026

Uh oh!

roidelapluie commented May 19, 2026

Uh oh!

krajorama commented May 20, 2026

Uh oh!

juliusv commented May 20, 2026

Uh oh!

juliusv left a comment

Uh oh!

krajorama commented May 21, 2026

Uh oh!

Uh oh!

roidelapluie commented May 21, 2026

Uh oh!

bwplotka left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

roidelapluie commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Which issue(s) does the PR fix:

Release notes for end users (ALL commits must be considered).

Uh oh!

krajorama commented May 19, 2026

Uh oh!

roidelapluie commented May 19, 2026

Uh oh!

krajorama commented May 19, 2026

Uh oh!

roidelapluie commented May 19, 2026

Uh oh!

krajorama commented May 20, 2026

Uh oh!

juliusv commented May 20, 2026

Uh oh!

juliusv left a comment

Choose a reason for hiding this comment

Uh oh!

krajorama commented May 21, 2026

Uh oh!

Uh oh!

roidelapluie commented May 21, 2026

Uh oh!

bwplotka left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

roidelapluie commented May 13, 2026 •

edited

Loading