Skip to content

Conversation

@mimir-github-bot
Copy link
Contributor

@mimir-github-bot mimir-github-bot bot commented Nov 12, 2025

Merge from prometheus/prometheus

This PR was automatically created by the merge-upstream-prometheus workflow

Details:

Changes:

This PR merges the latest changes from the upstream prometheus/prometheus main branch.


Note

Adds Alertmanager notification latency histogram and metric cleanup, fixes PromQL anchored changes/resets and test harness, ensures +Inf bucket in histogram conversion, corrects TSDB OOO delta metric registration, and tweaks operator docs.

  • Notifier:
    • Add prometheus_notifications_latency_histogram_seconds and keep summary (latency_seconds); observe both and clean up per-Alertmanager metrics on removal.
  • PromQL:
    • Improve anchored selector handling in changes()/resets() via pickFirstSampleIndex (now returns found flag).
    • Test harness accepts expected failures during query construction; update expected results in extended_vectors.test.
  • TSDB:
    • Properly register prometheus_tsdb_sample_ooo_delta.
  • Formatting:
    • Ensure classic histogram write conversion adds missing +Inf bucket; add unit tests.
  • Docs:
    • Operators doc: adjust heading to limitk (was limitk and limit_ratio).
  • Changelog:
    • Note new template function and TSDB bugfix.

Written by Cursor Bugbot for commit d999872. This will update automatically on new commits. Configure here.

roidelapluie and others added 10 commits November 5, 2025 12:07
…n samples outside range

The funcResets and funcChanges functions now correctly return no result when all float samples are at or before the range start for anchored selectors, consistent with the behavior of rate/increase functions.

Signed-off-by: Julien Pivotto <[email protected]>
Signed-off-by: Charles Korn <[email protected]>
docs: fix heading for `limitk` docs
promql: fix resets/changes to return empty for anchored selectors when samples outside range
* register missing metric prometheus_tsdb_sample_ooo_delta

Signed-off-by: yeya24 <[email protected]>

* changelog

Signed-off-by: yeya24 <[email protected]>

---------

Signed-off-by: yeya24 <[email protected]>
PromQL: Allow for promql tests to consider expected fail message during query preparation
…t (#15864)

* Add +Inf bucket in MetricFamiliesToWriteRequest if not present

Signed-off-by: Clark McCauley <[email protected]>
This metric can be used to create alerting based on how many
notifications finish or do not finish within a certain amount of time.

Change-Id: afbf3d8ceb3994c7d6220389353cff92
Signed-Off-By: Kevin Hellemun <[email protected]>
Co-authored-by: Björn Rabenstein <[email protected]>

---------

Signed-off-by: Kevin Hellemun <[email protected]>
Co-authored-by: Björn Rabenstein <[email protected]>
@CLAassistant
Copy link

CLAassistant commented Nov 12, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
4 out of 8 committers have signed the CLA.

✅ roidelapluie
✅ charleskorn
✅ beorn7
✅ tcp13equals2
❌ yeya24
❌ mimir-github-bot[bot]
❌ OGKevin
❌ clarkmcc
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

@mimir-vendoring mimir-vendoring bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm approving this upstream merge PR.
This PR merges changes from prometheus/prometheus upstream repository.
Related GitHub action is defined here.

@mimir-vendoring mimir-vendoring bot enabled auto-merge November 12, 2025 00:21
if err := cmd.checkExpectedFailure(err); err == nil {
return nil
}
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Generic error hides specific failure cause

When query creation fails and the test expects a failure, if checkExpectedFailure returns a non-nil error (indicating the actual error doesn't match expectations), the code falls through and returns a generic "error creating range query" message instead of the specific mismatch error from checkExpectedFailure. This loses information about why the failure didn't match. The error from checkExpectedFailure should be returned directly, similar to how it's handled at line 1444.

Fix in Cursor Fix in Web

if err := cmd.checkExpectedFailure(err); err == nil {
return nil
}
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Generic error masks specific failure reasons.

When query creation fails and the test expects a failure, if checkExpectedFailure returns a non-nil error (indicating the actual error doesn't match expectations), the code falls through and returns a generic "error creating instant query" message instead of the specific mismatch error from checkExpectedFailure. This loses information about why the failure didn't match. The error from checkExpectedFailure should be returned directly, similar to how it's handled at line 1492.

Fix in Cursor Fix in Web

@mimir-vendoring mimir-vendoring bot merged commit 1d13e85 into main Nov 12, 2025
29 of 30 checks passed
@mimir-vendoring mimir-vendoring bot deleted the bot/main/merge-upstream-main-202511120019 branch November 12, 2025 00:49
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.

8 participants