chore(monitoring): update monitoring stack#11
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
from
June 8, 2026 11:35
db6860f to
6dbff35
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
2 times, most recently
from
June 12, 2026 16:56
286b1a9 to
0177c9d
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
2 times, most recently
from
June 23, 2026 13:56
47057ec to
3805bb9
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
4 times, most recently
from
July 6, 2026 20:00
0f81fb4 to
dd2a87f
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
3 times, most recently
from
July 21, 2026 17:57
c558f4e to
ec3b12c
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
from
July 22, 2026 12:16
ec3b12c to
f6859f0
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
3c00966→d69d04713.0.2→13.1.1v0.32.1→v0.33.1v1.144.0→v1.148.0v1.144.0→v1.148.0v1.144.0→v1.148.0Release Notes
grafana/grafana (docker.io/grafana/grafana)
v13.1.1v13.1.0Features and enhancements
aria-pressedstate toFilterPill#123069, @ashharrison90groupBylabels in alerts #122983, @yuri-tceretianfetchInitialRowsto improve async utilisation #123278, @adamyeatstags.namewhenaliasSubwrapping is detected #122277, @adamyeatsen-USlocalization resources from loading #125327, @hugohaggmark_folder.jsonwhen creating dashboards in new folders #126042, @ferruvich_folder.jsonwhen moving dashboards into new folders #126552, @ferruvichBug fixes
ResourceFieldmodal #123072, @ashharrison90Select/Comboboxmenus with the keyboard #122133, @ashharrison90Breaking changes
Plugin development fixes & changes
v13.0.4: 13.0.4Download page
What's new highlights
Features and enhancements
Bug fixes
v13.0.3Features and enhancements
_folder.jsonwhen creating dashboards in new folders #126323, @ferruvich_folder.jsonwhen moving dashboards into new folders #126676, @ferruvichBug fixes
prometheus/alertmanager (docker.io/prom/alertmanager)
v0.33.1: 0.33.1 / 2026-07-04Compare Source
notification_reasonfield in webhook documentation (#5329)v0.33.0: 0.33.0 / 2026-06-12Compare Source
group-key-in-metricsfeature flag. #5047AlertMarker,GroupMarkertomarkerpackage. #5047alertmanager_marked_alerts. #5047typespackage:MemMarker,AlertState*,AlertStatus. #5047receiver_matchersfilter to/api/v2/receivers,/api/v2/alerts, and/api/v2/alerts/groups. #5152--enable-feature=event-recorder, with file, webhook, and kafka outputs. #5072, #5246use_aws_http_clientconfig option to the sns notifier. #5178resolve_transitionis not set. #4821wont_fix_resolutionJQL to prevent duplicate issue creation. #5185AWS_CA_BUNDLEenv variable for the sns notifier. #5178v0.32.2: 0.32.2 / 2026-06-05Compare Source
VictoriaMetrics/VictoriaMetrics (docker.io/victoriametrics/victoria-metrics)
v1.148.0Compare Source
v1.148.0
Released at 2026-07-17
SECURITY: upgrade Go builder from Go1.26.4 to Go1.26.5. See the list of issues addressed in Go1.26.5.
FEATURE: MetricsQL: support
fillmodifiers to allow missing series on either side of a binary operation to be filled with a provided default value. See #10598.FEATURE: vmagent and vmsingle: support scraping metrics over Unix domain sockets. The socket path can be configured via the
__unix_socket__target label. See #11156. Thanks to @vinyas-bharadwaj for contribution.FEATURE: vmagent and vmsingle: Improve background discovery performance for http_sd discovery. See #8838.
FEATURE: vmagent and vmsingle: allow overriding
max_scrape_sizeon a per-target basis via the__max_scrape_size__label during target relabeling. See #11188.FEATURE: vmstorage and vmsingle: add
-maxBackfillAgecommand-line flag for limiting ingestion of samples with historical timestamps, for example, when older data has been moved between storage tiers (nvme/hdd, hot/cold). See #11199. Thanks to @AshwinRamaniPsg for contribution.FEATURE: vmagent: automatically preload relabeling rules configured via
-remoteWrite.relabelConfigand-remoteWrite.urlRelabelConfigin the metrics relabel debug UI. See #9918.BUGFIX:
vminsertin VictoriaMetrics cluster: Now drops metadata blocks when communicating with vmstorage nodes over the legacy RPC protocol. To avoid this limitation, upgradevmstorageto a version that supports the new RPC protocol (>= v1.137.0). See #11146.BUGFIX: vmbackup and vmbackupmanager: retry S3 requests failing with
HTTP 429status code orTooManyRequestserror code. Previously such requests were not retried, so a short burst of rate limiting would fail the whole backup. See #11218. Thanks to @gautamrizwani for contribution.BUGFIX:
vmselectin VictoriaMetrics cluster: properly apply limit to metrics metadata response. See #11139.BUGFIX: vmagent: fix a possible data race when processing OpenTelemetry metadata. See #11238. Thanks to @nevgeny for contribution.
BUGFIX: vmagent: flush pending persistent queue data to chunk file before updating the metadata. This prevents the metadata writer offset from getting ahead of the chunk file size and avoids losing the persistent queue after an unclean shutdown. See #11192.
BUGFIX: vmagent: atomically write persistent queue metainfo to prevent possible file corruption on ungraceful shutdown. See #11192.
BUGFIX: vmagent: fix increased CPU and memory usage when
-remoteWrite.urlRelabelConfigor-remoteWrite.streamAggr.configflags are used. The bug was introduced in #10854 and existed since v1.147.0. See #11250.BUGFIX: vmui: preserve newline formatting in alert and rule annotations on the Alerting page. See #11171.
BUGFIX: vmui: hide
Total metric namesstats on Cardinality Explorer page when user selects a specific metric or label to focus. See [#11154](https://redirect.github.com/VictorConfiguration
📅 Schedule: (in timezone Europe/Paris)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.