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
db6860f to
6dbff35
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
2 times, most recently
from
286b1a9 to
0177c9d
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
2 times, most recently
from
47057ec to
3805bb9
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
3 times, most recently
from
d583237 to
0f81fb4
Compare
renovate
Bot
force-pushed
the
renovate/monitoring-stack
branch
from
0f81fb4 to
dd2a87f
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→60c783913.0.2→13.1.0v0.32.1→v0.33.1v1.144.0→v1.147.0v1.144.0→v1.147.0v1.144.0→v1.147.0Release Notes
grafana/grafana (docker.io/grafana/grafana)
v13.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.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.147.0Compare Source
v1.147.0
Released at 2026-07-03
SECURITY: upgrade base docker image (Alpine) from 3.23.4 to 3.24.1. See Alpine 3.24.1 release notes.
FEATURE: vmauth: add
default_vm_access_claimfield intojwtsection of auth config. It could be used at JWT claim placeholders, ifJWTtoken doesn't havevm_accessclaim. See #11054.FEATURE: vmagent: reduces CPU usage by 10% at sharding among remote storages. See #11113. Thanks to @bennf for contribution.
FEATURE: vmagent,
vminsertin VictoriaMetrics cluster and vmsingle: introduce64KiBsize limit formetric metadatafields -Unit,HelpandMetricFamilyName. See #11128.FEATURE: vmagent and vmsingle: reduce CPU usage for storing scrape target labels. See #10919.
FEATURE: vmsingle and
vmselectin VictoriaMetrics cluster: addoptimize_repeated_binary_op_subexprs=1query arg to /api/v1/query_range for executing binary operator sides sequentially when they share the same optimized aggregate rollup result expression. This allows the second side to reuse rollup result cache populated by the first side. See #10575. Thanks to @xhebox for the contribution.FEATURE: vmauth: prevent possible password brute-force attacks with an artificial 2-3 second delay as recommended by OWASP. See #11180.
FEATURE: alerts: add
InvalidAuthTokenRequestErrorsalerting rule to vmauth alerts. The new rule notifies when vmauth receives requests with invalid or missing auth tokens, which may indicate a client misconfiguration, expired token use, or brute-force attack. See #11180.FEATURE: vmsingle: Add the support of vmselect RPC to vmsingle so that single node can be queried by a vmselect from a vmcluster deployment. See 4328 and 10926.
FEATURE: vmauth: allow log requests with missing or invalid auth tokens to access log. This is useful for identifying
remote_addrIPs performing brute-force attacks. See #11180.FEATURE: vmauth: fall through to
unauthorized_userwhen a JWT token has novm_accessclaim and nodefault_vm_access_claimis configured. Previously, vmauth returned401 Unauthorizedimmediately in this case, which preventedunauthorized_userfrom handling such requests. See #5740.FEATURE: MetricsQL: improve the selection algorithm of buckets_limit to remove consecutive empty buckets at the beginning and end to obtain more accurate min and max values. See #10417.
FEATURE: vmalert: expose
vmalert_group_rule_results_limitmetric to indicate the number of alerts or recording results that a single rule within the group can produce. See #11179. Thanks to @vinyas-bharadwaj for the contribution.FEATURE: alerts: add
AlertingRuleResultsApproachingLimitandRecordingRuleResultsApproachingLimitalerting rules to vmalert alerts. These alerts notify when a rule's last evaluation samples exceed 90% of the configured group results limit. See #11179. Thanks to @vinyas-bharadwaj for the contribution.BUGFIX: all VictoriaMetrics components: cancel in-flight HTTP requests shortly before
-http.maxGracefulShutdownDurationelapses during graceful shutdown, so they can drain and the shutdown completes cleanly within that window instead of timing out and exiting vialogger.Fatalf->os.Exit. This prevents skipping the storage flush and losing in-memory data when long-lived requests are in flight (such as VictoriaLogs live tailing). See #1502.BUGFIX:
vminsertin VictoriaMetrics cluster and vmsingle: properly check values range for the limits configured with flags-maxLabelsPerTimeseries,-maxLabelNameLenand-maxLabelValueLen. It must be in range1..65535. See #11128.BUGFIX:
vminsertin VictoriaMetrics cluster: fixes unexpected rare rerouting. See #11162.BUGFIX:
vmselectin VictoriaMetrics cluster: propagate cache reset operation toselectNodewhen/internal/resetRollupResultCacheis called. Previously, the propagation only happened when thedelete_seriesAPI was called. See [#11112](https://redirect.github.com/VictoriaMetrics/VictoriaMetriConfiguration
📅 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.