Repository: VictoriaMetrics/VictoriaMetrics
Pull request #7298 (2024-10-18 13:28:34)

vmalert: properly set `group_name` and `file` fields for recording rules
### Describe Your Changes

Adds group_name and file fields for recording rules where they were previously left blank.

See issue #7297

### Checklist

The following checks are **mandatory**:

- [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/).


antoinedeschenes: @Haleygo just fixed the commit signature issues. Workflow requires reapproval 🙏 

Patch:
diff --git a/app/vmalert/web_types.go b/app/vmalert/web_types.go
index 639236591..31423b8f2 100644
--- a/app/vmalert/web_types.go
+++ b/app/vmalert/web_types.go
@@ -215,8 +215,10 @@ func recordingToAPI(rr *rule.RecordingRule) apiRule {
 		Updates:           rule.GetAllRuleState(rr),
 
 		// encode as strings to avoid rounding
-		ID:      fmt.Sprintf("%d", rr.ID()),
-		GroupID: fmt.Sprintf("%d", rr.GroupID),
+		ID:        fmt.Sprintf("%d", rr.ID()),
+		GroupID:   fmt.Sprintf("%d", rr.GroupID),
+		GroupName: rr.GroupName,
+		File:      rr.File,
 	}
 	if lastState.Err != nil {
 		r.LastError = lastState.Err.Error()
diff --git a/deployment/docker/docker-compose-cluster.yml b/deployment/docker/docker-compose-cluster.yml
index 8828adcdb..088bb8681 100644
--- a/deployment/docker/docker-compose-cluster.yml
+++ b/deployment/docker/docker-compose-cluster.yml
@@ -4,7 +4,7 @@ services:
   #  And forward them to --remoteWrite.url
   vmagent:
     container_name: vmagent
-    image: victoriametrics/vmagent:v1.104.0
+    image: victoriametrics/vmagent:v1.105.0
     depends_on:
       - "vminsert"
     ports:
@@ -13,8 +13,8 @@ services:
       - vmagentdata:/vmagentdata
       - ./prometheus-cluster.yml:/etc/prometheus/prometheus.yml
     command:
-      - '--promscrape.config=/etc/prometheus/prometheus.yml'
-      - '--remoteWrite.url=http://vminsert:8480/insert/0/prometheus/'
+      - "--promscrape.config=/etc/prometheus/prometheus.yml"
+      - "--remoteWrite.url=http://vminsert:8480/insert/0/prometheus/"
     restart: always
 
   # Grafana instance configured with VictoriaMetrics as datasource
@@ -39,7 +39,7 @@ services:
   # where N is number of vmstorages (2 in this case).
   vmstorage-1:
     container_name: vmstorage-1
-    image: victoriametrics/vmstorage:v1.104.0-cluster
+    image: victoriametrics/vmstorage:v1.105.0-cluster
     ports:
       - 8482
       - 8400
@@ -47,11 +47,11 @@ services:
     volumes:
       - strgdata-1:/storage
     command:
-      - '--storageDataPath=/storage'
+      - "--storageDataPath=/storage"
     restart: always
   vmstorage-2:
     container_name: vmstorage-2
-    image: victoriametrics/vmstorage:v1.104.0-cluster
+    image: victoriametrics/vmstorage:v1.105.0-cluster
     ports:
       - 8482
       - 8400
@@ -59,20 +59,20 @@ services:
     volumes:
       - strgdata-2:/storage
     command:
-      - '--storageDataPath=/storage'
+      - "--storageDataPath=/storage"
     restart: always
 
   # vminsert is ingestion frontend. It receives metrics pushed by vmagent,
   # pre-process them and distributes across configured vmstorage shards.
   vminsert:
     container_name: vminsert
-    image: victoriametrics/vminsert:v1.104.0-cluster
+    image: victoriametrics/vminsert:v1.105.0-cluster
     depends_on:
       - "vmstorage-1"
       - "vmstorage-2"
     command:
-      - '--storageNode=vmstorage-1:8400'
-      - '--storageNode=vmstorage-2:8400'
+      - "--storageNode=vmstorage-1:8400"
+      - "--storageNode=vmstorage-2:8400"
     ports:
       - 8480:8480
     restart: always
@@ -81,27 +81,27 @@ services:
   # vmselect collects results from configured `--storageNode` shards.
   vmselect-1:
     container_name: vmselect-1
-    image: victoriametrics/vmselect:v1.104.0-cluster
+    image: victoriametrics/vmselect:v1.105.0-cluster
     depends_on:
       - "vmstorage-1"
       - "vmstorage-2"
     command:
-      - '--storageNode=vmstorage-1:8401'
-      - '--storageNode=vmstorage-2:8401'
-      - '--vmalert.proxyURL=http://vmalert:8880'
+      - "--storageNode=vmstorage-1:8401"
+      - "--storageNode=vmstorage-2:8401"
+      - "--vmalert.proxyURL=http://vmalert:8880"
     ports:
       - 8481
     restart: always
   vmselect-2:
     container_name: vmselect-2
-    image: victoriametrics/vmselect:v1.104.0-cluster
+    image: victoriametrics/vmselect:v1.105.0-cluster
     depends_on:
       - "vmstorage-1"
       - "vmstorage-2"
     command:
-      - '--storageNode=vmstorage-1:8401'
-      - '--storageNode=vmstorage-2:8401'
-      - '--vmalert.proxyURL=http://vmalert:8880'
+      - "--storageNode=vmstorage-1:8401"
+      - "--storageNode=vmstorage-2:8401"
+      - "--vmalert.proxyURL=http://vmalert:8880"
     ports:
       - 8481
     restart: always
@@ -112,14 +112,14 @@ services:
   # It can be used as an authentication proxy.
   vmauth:
     container_name: vmauth
-    image: victoriametrics/vmauth:v1.104.0
+    image: victoriametrics/vmauth:v1.105.0
     depends_on:
       - "vmselect-1"
       - "vmselect-2"
     volumes:
       - ./auth-cluster.yml:/etc/auth.yml
     command:
-      - '--auth.config=/etc/auth.yml'
+      - "--auth.config=/etc/auth.yml"
     ports:
       - 8427:8427
     restart: always
@@ -127,7 +127,7 @@ services:
   # vmalert executes alerting and recording rules
   vmalert:
     container_name: vmalert
-    image: victoriametrics/vmalert:v1.104.0
+    image: victoriametrics/vmalert:v1.105.0
     depends_on:
       - "vmauth"
     ports:
@@ -138,13 +138,13 @@ services:
       - ./alerts-vmagent.yml:/etc/alerts/alerts-vmagent.yml
       - ./alerts-vmalert.yml:/etc/alerts/alerts-vmalert.yml
     command:
-      - '--datasource.url=http://vmauth:8427/select/0/prometheus'
-      - '--remoteRead.url=http://vmauth:8427/select/0/prometheus'
-      - '--remoteWrite.url=http://vminsert:8480/insert/0/prometheus'
-      - '--notifier.url=http://alertmanager:9093/'
-      - '--rule=/etc/alerts/*.yml'
+      - "--datasource.url=http://vmauth:8427/select/0/prometheus"
+      - "--remoteRead.url=http://vmauth:8427/select/0/prometheus"
+      - "--remoteWrite.url=http://vminsert:8480/insert/0/prometheus"
+      - "--notifier.url=http://alertmanager:9093/"
+      - "--rule=/etc/alerts/*.yml"
       # display source of alerts in grafana
-      - '-external.url=http://127.0.0.1:3000' #grafana outside container
+      - "-external.url=http://127.0.0.1:3000" #grafana outside container
       - '--external.alert.source=explore?orgId=1&left={"datasource":"VictoriaMetrics","queries":[{"expr":{{.Expr|jsonEscape|queryEscape}},"refId":"A"}],"range":{"from":"{{ .ActiveAt.UnixMilli }}","to":"now"}}'
     restart: always
 
@@ -156,7 +156,7 @@ services:
     volumes:
       - ./alertmanager.yml:/config/alertmanager.yml
     command:
-      - '--config.file=/config/alertmanager.yml'
+      - "--config.file=/config/alertmanager.yml"
     ports:
       - 9093:9093
     restart: always
diff --git a/deployment/docker/docker-compose-victorialogs.yml b/deployment/docker/docker-compose-victorialogs.yml
index 3e6ed02d5..b18c05718 100644
--- a/deployment/docker/docker-compose-victorialogs.yml
+++ b/deployment/docker/docker-compose-victorialogs.yml
@@ -36,8 +36,8 @@ services:
     networks:
       - vm_net
 
-#  VictoriaLogs instance, a single process responsible for
-#  storing logs and serving read queries.
+  #  VictoriaLogs instance, a single process responsible for
+  #  storing logs and serving read queries.
   victorialogs:
     container_name: victorialogs
     image: docker.io/victoriametrics/victoria-logs:v0.37.0-victorialogs
@@ -55,7 +55,7 @@ services:
   # scraping, storing metrics and serve read requests.
   victoriametrics:
     container_name: victoriametrics
-    image: victoriametrics/victoria-metrics:v1.104.0
+    image: victoriametrics/victoria-metrics:v1.105.0
     ports:
       - 8428:8428
     volumes:
@@ -72,7 +72,7 @@ services:
   # vmalert executes alerting and recording rules
   vmalert:
     container_name: vmalert
-    image: victoriametrics/vmalert:v1.104.0
+    image: victoriametrics/vmalert:v1.105.0
     depends_on:
       - "victoriametrics"
       - "alertmanager"
diff --git a/deployment/docker/docker-compose.yml b/deployment/docker/docker-compose.yml
index 1b9584191..341b3d321 100644
--- a/deployment/docker/docker-compose.yml
+++ b/deployment/docker/docker-compose.yml
@@ -4,7 +4,7 @@ services:
   #  And forward them to --remoteWrite.url
   vmagent:
     container_name: vmagent
-    image: victoriametrics/vmagent:v1.104.0
+    image: victoriametrics/vmagent:v1.105.0
     depends_on:
       - "victoriametrics"
     ports:
@@ -22,7 +22,7 @@ services:
   # storing metrics and serve read requests.
   victoriametrics:
     container_name: victoriametrics
-    image: victoriametrics/victoria-metrics:v1.104.0
+    image: victoriametrics/victoria-metrics:v1.105.0
     ports:
       - 8428:8428
       - 8089:8089
@@ -65,7 +65,7 @@ services:
   # vmalert executes alerting and recording rules
   vmalert:
     container_name: vmalert
-    image: victoriametrics/vmalert:v1.104.0
+    image: victoriametrics/vmalert:v1.105.0
     depends_on:
       - "victoriametrics"
       - "alertmanager"
diff --git a/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml b/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
index 75ffe1852..e073cc2d5 100644
--- a/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
+++ b/deployment/docker/vmanomaly/vmanomaly-integration/docker-compose.yml
@@ -1,7 +1,7 @@
 services:
   vmagent:
     container_name: vmagent
-    image: victoriametrics/vmagent:v1.104.0
+    image: victoriametrics/vmagent:v1.105.0
     depends_on:
       - "victoriametrics"
     ports:
@@ -18,7 +18,7 @@ services:
 
   victoriametrics:
     container_name: victoriametrics
-    image: victoriametrics/victoria-metrics:v1.104.0
+    image: victoriametrics/victoria-metrics:v1.105.0
     ports:
       - 8428:8428
     volumes:
@@ -48,10 +48,9 @@ services:
       - vm_net
     restart: always
 
-
   vmalert:
     container_name: vmalert
-    image: victoriametrics/vmalert:v1.104.0
+    image: victoriametrics/vmalert:v1.105.0
     depends_on:
       - "victoriametrics"
     ports:
@@ -73,7 +72,7 @@ services:
     restart: always
   vmanomaly:
     container_name: vmanomaly
-    image: victoriametrics/vmanomaly:v1.17.1
+    image: victoriametrics/vmanomaly:v1.17.2
     depends_on:
       - "victoriametrics"
     ports:
diff --git a/deployment/logs-benchmark/docker-compose.yml b/deployment/logs-benchmark/docker-compose.yml
index 4b5ce36f7..aabd0fcf1 100644
--- a/deployment/logs-benchmark/docker-compose.yml
+++ b/deployment/logs-benchmark/docker-compose.yml
@@ -1,4 +1,4 @@
-version: '3'
+version: "3"
 
 services:
   # Run `make package-victoria-logs` to build victoria-logs image
@@ -7,7 +7,7 @@ services:
     volumes:
       - vlogs:/vlogs
     ports:
-      - '9428:9428'
+      - "9428:9428"
     command:
       - -storageDataPath=/vlogs
 
@@ -30,10 +30,10 @@ services:
       - /sys:/host/sys:ro
       - /:/rootfs:ro
     command:
-      - '--path.procfs=/host/proc'
-      - '--path.rootfs=/rootfs'
-      - '--path.sysfs=/host/sys'
-      - '--collector.filesystem.mount-points-exclude=^/(sys|proc|dev|host|etc)($$|/)'
+      - "--path.procfs=/host/proc"
+      - "--path.rootfs=/rootfs"
+      - "--path.sysfs=/host/sys"
+      - "--collector.filesystem.mount-points-exclude=^/(sys|proc|dev|host|etc)($$|/)"
 
   du-exporter:
     image: ghcr.io/dundee/disk_usage_exporter/disk_usage_exporter-c4084307c537335c2ddb6f4b9b527422:latest
@@ -43,12 +43,12 @@ services:
       - /var/lib/docker/volumes:/var/lib/docker/volumes:ro
       - ./du/config.yml:/config.yml:ro
     command:
-      - '--config=/config.yml'
+      - "--config=/config.yml"
 
   vmsingle:
-    image: victoriametrics/victoria-metrics:v1.104.0
+    image: victoriametrics/victoria-metrics:v1.105.0
     ports:
-      - '8428:8428'
+      - "8428:8428"
     command:
       - -storageDataPath=/vmsingle
       - -promscrape.config=/promscrape.yml
diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md
index e3a59bfa7..781485a2e 100644
--- a/docs/Cluster-VictoriaMetrics.md
+++ b/docs/Cluster-VictoriaMetrics.md
@@ -1091,7 +1091,7 @@ Report bugs and propose new features [here](https://github.com/VictoriaMetrics/V
 
 Below is the output for `/path/to/vminsert -help`:
 
-```
+```shellhelp
   -blockcache.missesBeforeCaching int
      The number of cache misses before putting the block into cache. Higher values may reduce indexdb/dataBlocks cache size at the cost of higher CPU and disk read usage (default 2)
   -cacheExpireDuration duration
diff --git a/docs/README.md b/docs/README.md
index cf3561fa4..f6f327c20 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -2790,7 +2790,7 @@ Files included in each folder:
 
 Pass `-help` to VictoriaMetrics in order to see the list of supported command-line flags with their description:
 
-```sh
+```shellhelp
   -bigMergeConcurrency int
      Deprecated: this flag does nothing
   -blockcache.missesBeforeCaching int
diff --git a/docs/anomaly-detection/CHANGELOG.md b/docs/anomaly-detection/CHANGELOG.md
index 0a4f6fee4..dd01a1df4 100644
--- a/docs/anomaly-detection/CHANGELOG.md
+++ b/docs/anomaly-detection/CHANGELOG.md
@@ -11,10 +11,19 @@ aliases:
 ---
 Please find the changelog for VictoriaMetrics Anomaly Detection below.
 
+## v1.17.2
+Released: 2024-10-22
+
+- IMPROVEMENT: Added `vmanomaly_version_info` (service) and `vmanomaly_ui_version_info` (vmui) gauges to self-monitoring metrics.
+- IMPROVEMENT: Added `instance` and `job` labels to [pushed](https://docs.victoriametrics.com/keyconcepts/#push-model) metrics so they have the same labels as vmanomaly metrics that are [pulled](https://docs.victoriametrics.com/keyconcepts/#pull-model)/scraped. Metric labels can be customized via the [`extra_labels` argument](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/?highlight=extra_labels#push-config-parameters). By default job label will be `vmanomaly` and the instance label will be `f'{hostname}:{vmanomaly_port}`. See [monitoring.push](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/#push-config-parameters) for examples and details.
+- IMPROVEMENT: Added a subsection to [monitoring](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/#logs-generated-by-vmanomaly) page with detailed per-component service logs, including reader and writer logs, error handling, metrics updates, and multi-tenancy warnings.
+- IMPROVEMENT: Added a new [Command-line arguments](https://docs.victoriametrics.com/anomaly-detection/quickstart/#command-line-arguments) subsection to the [Quickstart guide](https://docs.victoriametrics.com/anomaly-detection/quickstart/), providing details on available options for configuring `vmanomaly`.
+
+
 ## v1.17.1
 Released: 2024-10-18
 
-- FIX: Fixed an issue occurred when [Prophet model](https://docs.victoriametrics.com/anomaly-detection/components/models/#prophet) is trained on *constant* data (data consisting of the same value and no variation across time). The bug prevented the `fit` stage from completing successfully, resulting in the model instance not being stored in the model registry, after automated model cleanup was addded in [v1.17.0](#1170). 
+- FIX: [Prophet models](https://docs.victoriametrics.com/anomaly-detection/components/models/#prophet) no longer fail to train on *constant* data, data consisting of the same value and no variation across time. The bug prevented the `fit` stage from completing successfully, resulting in the model instance not being stored in the model registry, after automated model cleanup was added in [v1.17.0](#1170).
 
 ## v1.17.0
 Released: 2024-10-17
diff --git a/docs/anomaly-detection/FAQ.md b/docs/anomaly-detection/FAQ.md
index 5202d362f..b80e5e281 100644
--- a/docs/anomaly-detection/FAQ.md
+++ b/docs/anomaly-detection/FAQ.md
@@ -132,7 +132,7 @@ services:
   # ...
   vmanomaly:
     container_name: vmanomaly
-    image: victoriametrics/vmanomaly:v1.17.1
+    image: victoriametrics/vmanomaly:v1.17.2
     # ...
     ports:
       - "8490:8490"
@@ -230,7 +230,7 @@ P.s. `infer` data volume will remain the same for both models, so it does not af
 
 If you're dealing with a large query in the `queries` argument of [VmReader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader) (especially when running [within a scheduler using a long](https://docs.victoriametrics.com/anomaly-detection/components/scheduler/?highlight=fit_window#periodic-scheduler) `fit_window`), you may encounter issues such as query timeouts (due to the `search.maxQueryDuration` server limit) or rejections (if the `search.maxPointsPerTimeseries` server limit is exceeded). 
 
-We recommend upgrading to [v1.17.1](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1171), which introduced the `max_points_per_query` argument (both global and [query-specific](https://docs.victoriametrics.com/anomaly-detection/components/reader/#per-query-parameters)) for the [VmReader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader). This argument overrides how `search.maxPointsPerTimeseries` flag handling (introduced in [v1.14.1](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1141)) is used in `vmanomaly` for splitting long `fit_window` queries into smaller sub-intervals. This helps users avoid hitting the `search.maxQueryDuration` limit for individual queries by distributing initial query across multiple subquery requests with minimal overhead.
+We recommend upgrading to [v1.17.2](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1171), which introduced the `max_points_per_query` argument (both global and [query-specific](https://docs.victoriametrics.com/anomaly-detection/components/reader/#per-query-parameters)) for the [VmReader](https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader). This argument overrides how `search.maxPointsPerTimeseries` flag handling (introduced in [v1.14.1](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1141)) is used in `vmanomaly` for splitting long `fit_window` queries into smaller sub-intervals. This helps users avoid hitting the `search.maxQueryDuration` limit for individual queries by distributing initial query across multiple subquery requests with minimal overhead.
 
 By splitting long `fit_window` queries into smaller sub-intervals, this helps avoid hitting the `search.maxQueryDuration` limit, distributing the load across multiple subquery requests with minimal overhead. To resolve the issue, reduce `max_points_per_query` to a value lower than `search.maxPointsPerTimeseries` until the problem is gone:
 
diff --git a/docs/anomaly-detection/Overview.md b/docs/anomaly-detection/Overview.md
index 1d791930b..24477da3c 100644
--- a/docs/anomaly-detection/Overview.md
+++ b/docs/anomaly-detection/Overview.md
@@ -229,7 +229,7 @@ This will expose metrics at `http://0.0.0.0:8080/metrics` page.
 To use *vmanomaly* you need to pull docker image:
 
 ```sh
-docker pull victoriametrics/vmanomaly:v1.17.1
+docker pull victoriametrics/vmanomaly:v1.17.2
 ```
 
 > Note: please check what is latest release in [CHANGELOG](https://docs.victoriametrics.com/anomaly-detection/changelog/)
@@ -239,7 +239,7 @@ docker pull victoriametrics/vmanomaly:v1.17.1
 You can put a tag on it for your convenience:
 
 ```sh
-docker image tag victoriametrics/vmanomaly:v1.17.1 vmanomaly
+docker image tag victoriametrics/vmanomaly:v1.17.2 vmanomaly
 ```
 Here is an example of how to run *vmanomaly* docker container with [license file](#licensing):
 
diff --git a/docs/anomaly-detection/QuickStart.md b/docs/anomaly-detection/QuickStart.md
index 154b30268..e82de0ad5 100644
--- a/docs/anomaly-detection/QuickStart.md
+++ b/docs/anomaly-detection/QuickStart.md
@@ -25,6 +25,30 @@ The following options are available:
 
 > **Note**: Starting from [v1.16.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1160), a similar optimization is available for data read from VictoriaMetrics TSDB. See instructions [here](https://docs.victoriametrics.com/anomaly-detection/faq/#on-disk-mode).
 
+### Command-line arguments
+
+The `vmanomaly` service supports several command-line arguments to configure its behavior, including options for licensing, logging levels, and more. These arguments can be passed when starting the service via Docker or any other setup. Below is the list of available options:
+
+
+```shellhelp
+VictoriaMetrics Anomaly Detection Service
+
+positional arguments:
+  config                YAML config file. Multiple files will override each other's top level values (aka shallow merge), so multiple configs can be combined.
+
+options:
+  -h                    show this help message and exit
+  --license STRING      License key for VictoriaMetrics Enterprise. See https://victoriametrics.com/products/enterprise/trial/ to obtain a trial license.
+  --licenseFile PATH    Path to file with license key for VictoriaMetrics Enterprise. See https://victoriametrics.com/products/enterprise/trial/ to obtain a trial license.
+  --license.forceOffline 
+                        Whether to force offline verification for VictoriaMetrics Enterprise license key, which has been passed either via -license or via -licenseFile command-line flag.
+                        The issued license key must support offline verification feature. Contact info@victoriametrics.com if you need offline license verification.
+  --loggerLevel {FATAL,WARNING,ERROR,DEBUG,INFO}
+                        Minimum level to log. Possible values: DEBUG, INFO, WARNING, ERROR, FATAL.
+```
+
+You can specify these options when running `vmanomaly` to fine-tune logging levels or handle licensing configurations, as per your requirements.
+
 ### Docker
 
 > To run `vmanomaly`, you need to have VictoriaMetrics Enterprise license. You can get a trial license key [**here**](https://victoriametrics.com/products/enterprise/trial/).
@@ -34,13 +58,13 @@ Below are the steps to get `vmanomaly` up and running inside a Docker container:
 1. Pull Docker image:
 
 ```sh
-docker pull victoriametrics/vmanomaly:v1.17.1
+docker pull victoriametrics/vmanomaly:v1.17.2
 ```
 
 2. (Optional step) tag the `vmanomaly` Docker image:
 
 ```sh
-docker image tag victoriametrics/vmanomaly:v1.17.1 vmanomaly
+docker image tag victoriametrics/vmanomaly:v1.17.2 vmanomaly
 ```
 
 3. Start the `vmanomaly` Docker container with a *license file*, use the command below.
@@ -52,7 +76,8 @@ export YOUR_CONFIG_FILE_PATH=path/to/config/file
 docker run -it -v $YOUR_LICENSE_FILE_PATH:/license \
                -v $YOUR_CONFIG_FILE_PATH:/config.yml \
                vmanomaly /config.yml \
-               --licenseFile=/license
+               --licenseFile=/license \
+               --loggerLevel=INFO
 ```
 
 In case you found `PermissionError: [Errno 13] Permission denied:` in `vmanomaly` logs, set user/user group to 1000 in the run command above / in a docker-compose file:
@@ -64,7 +89,8 @@ docker run -it --user 1000:1000 \
                -v $YOUR_LICENSE_FILE_PATH:/license \
                -v $YOUR_CONFIG_FILE_PATH:/config.yml \
                vmanomaly /config.yml \
-               --licenseFile=/license
+               --licenseFile=/license \
+               --loggerLevel=INFO
 ```
 
 ```yaml
@@ -72,13 +98,14 @@ docker run -it --user 1000:1000 \
 services:
   # ...
   vmanomaly:
-    image: victoriametrics/vmanomaly:v1.17.1
+    image: victoriametrics/vmanomaly:v1.17.2
     volumes:
         $YOUR_LICENSE_FILE_PATH:/license
         $YOUR_CONFIG_FILE_PATH:/config.yml
     command:
       - "/config.yml"
       - "--licenseFile=/license"
+      - "--loggerLevel=INFO"
     # ...
 ```
 
diff --git a/docs/anomaly-detection/components/models.md b/docs/anomaly-detection/components/models.md
index 56ae1b4cc..85485b77e 100644
--- a/docs/anomaly-detection/components/models.md
+++ b/docs/anomaly-detection/components/models.md
@@ -962,7 +962,7 @@ monitoring:
 Let's pull the docker image for `vmanomaly`:
 
 ```sh
-docker pull victoriametrics/vmanomaly:v1.17.0
+docker pull victoriametrics/vmanomaly:v1.17.2
 ```
 
 Now we can run the docker container putting as volumes both config and model file:
@@ -976,7 +976,7 @@ docker run -it \
 -v $(PWD)/license:/license \
 -v $(PWD)/custom_model.py:/vmanomaly/model/custom.py \
 -v $(PWD)/custom.yaml:/config.yaml \
-victoriametrics/vmanomaly:v1.17.0 /config.yaml \
+victoriametrics/vmanomaly:v1.17.2 /config.yaml \
 --licenseFile=/license
 ```
 
diff --git a/docs/anomaly-detection/components/monitoring.md b/docs/anomaly-detection/components/monitoring.md
index 235e38f0d..362717b3d 100644
--- a/docs/anomaly-detection/components/monitoring.md
+++ b/docs/anomaly-detection/components/monitoring.md
@@ -226,6 +226,13 @@ For detailed guidance on configuring mTLS parameters such as `verify_tls`, `tls_
 
 ## Metrics generated by vmanomaly
 
+- [Startup metrics](#startup-metrics)
+- [Reader metrics](#reader-behaviour-metrics)
+- [Model metrics](#models-behaviour-metrics)
+- [Writer metrics](#writer-behaviour-metrics)
+
+### Startup metrics
+
 <table class="params">
     <thead>
         <tr>
@@ -243,15 +250,31 @@ For detailed guidance on configuring mTLS parameters such as `verify_tls`, `tls_
             <td>Gauge</td>
             <td>vmanomaly start time in UNIX time</td>
         </tr>
+        <tr>
+            <td>
+
+`vmanomaly_version_info`
+            </td>
+            <td>Gauge</td>
+            <td>vmanomaly version information, contained in `version` label. Added in [v1.17.2](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1172)</td>
+        </tr>
+        <tr>
+            <td>
+
+`vmanomaly_ui_version_info`
+            </td>
+            <td>Gauge</td>
+            <td>vmanomaly UI version information, contained in `version` label. Added in [v1.17.2](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1172)</td>
+        </tr>
     </tbody>
 </table>
 
-### Models Behaviour Metrics
+[Back to metric sections](#metrics-generated-by-vmanomaly)
+
+### Reader behaviour metrics
 Label names [description](#labelnames)
 
-> **Note**: There is a new label key `model_alias` introduced in multi-model support [v1.10.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1100). This label key adjustment was made to preserve unique label set production during writing produced metrics back to VictoriaMetrics.
-
-> **Note**: as a part of [self-monitoring](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/#metrics-generated-by-vmanomaly) metrics enchancement ([v.1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)), new metrics, like `vmanomaly_model_run_errors`, was added. Some of them changed the type (`Summary` -> `Histogram`), like `vmanomaly_model_run_duration_seconds`.
+> **Note**: additional labels (`scheduler_alias`, `preset`) were added to writer and reader metrics in [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170) to improve consistency across the components. Also, metrics `vmanomaly_reader_request_duration_seconds` and `vmanomaly_reader_response_parsing_seconds` changed their type to `Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)).
 
 <table class="params">
     <thead>
@@ -266,93 +289,86 @@ Label names [description](#labelnames)
         <tr>
             <td>
 
-`vmanomaly_model_runs`
-            </td>
-            <td>`Counter`</td>
-            <td>How many successful `stage` (`fit`, `infer`, `fit_infer`) runs occurred for models of class `model_alias` based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
-            <td>
-
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
-            </td>
-        </tr>
-        <tr>
-            <td>
-
-`vmanomaly_model_run_duration_seconds`
+`vmanomaly_reader_request_duration_seconds`
             </td>
-            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)) </td>
-            <td>The total time (in seconds) taken by model invocations during the `stage` (`fit`, `infer`, `fit_infer`), based on the results of the `query_key` query, for models of class `model_alias`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
+            <td>The total time (in seconds) taken by queries to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+`url`, `query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_model_datapoints_accepted`
+`vmanomaly_reader_responses` (named `vmanomaly_reader_response_count` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))
             </td>
             <td>`Counter`</td>
-            <td>The number of datapoints accepted (excluding NaN or Inf values) by models of class `model_alias` from the results of the `query_key` query during the `stage` (`infer`, `fit_infer`), within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The count of responses received from VictoriaMetrics `url` for the `query_key` query, categorized by `code`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+`url`, `query_key`, `code`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_model_datapoints_produced`
+`vmanomaly_reader_received_bytes`
             </td>
             <td>`Counter`</td>
-            <td>The number of datapoints generated by models of class `model_alias` during the `stage` (`infer`, `fit_infer`) based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of bytes received in responses for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+`query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_models_active`
+`vmanomaly_reader_response_parsing_seconds`
             </td>
-            <td>`Gauge`</td>
-            <td>The number of model instances of class `model_alias` currently available for inference for the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
+            <td>The total time (in seconds) taken for data parsing at each `step` (json, dataframe) for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`query_key`, `model_alias`, `scheduler_alias`, `preset`
+`step`, `query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_model_runs_skipped`
+`vmanomaly_reader_timeseries_received`
             </td>
             <td>`Counter`</td>
-            <td>The number of times model runs (of class `model_alias`) were skipped in expected situations (e.g., no data for fitting/inference, or no new data to infer on) during the `stage` (`fit`, `infer`, `fit_infer`), based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of timeseries received from VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+`query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_model_run_errors`
+`vmanomaly_reader_datapoints_received`
             </td>
             <td>`Counter`</td>
-            <td>The number of times model runs (of class `model_alias`) failed due to internal service errors during the `stage` (`fit`, `infer`, `fit_infer`), based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of datapoints received from VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
-`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+
+`query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
     </tbody>
 </table>
 
-### Writer Behaviour Metrics
+[Back to metric sections](#metrics-generated-by-vmanomaly)
+
+### Models behaviour metrics
 Label names [description](#labelnames)
 
-> **Note**: additional labels (`scheduler_alias`, `preset`) were added to writer and reader metrics in [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170) to improve consistency across the components. Also, metrics `vmanomaly_writer_request_duration_seconds` and `vmanomaly_writer_request_serialize_seconds` changed their type to `Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)).
+> **Note**: There is a new label key `model_alias` introduced in multi-model support [v1.10.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1100). This label key adjustment was made to preserve unique label set production during writing produced metrics back to VictoriaMetrics.
+
+> **Note**: as a part of [self-monitoring](https://docs.victoriametrics.com/anomaly-detection/components/monitoring/#metrics-generated-by-vmanomaly) metrics enchancement ([v.1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)), new metrics, like `vmanomaly_model_run_errors`, was added. Some of them changed the type (`Summary` -> `Histogram`), like `vmanomaly_model_run_duration_seconds`.
 
 <table class="params">
     <thead>
@@ -367,81 +383,96 @@ Label names [description](#labelnames)
         <tr>
             <td>
 
-`vmanomaly_writer_request_duration_seconds`
+`vmanomaly_model_runs`
             </td>
-            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
-            <td>The total time (in seconds) taken by write requests to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.
-</td>
+            <td>`Counter`</td>
+            <td>How many successful `stage` (`fit`, `infer`, `fit_infer`) runs occurred for models of class `model_alias` based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`url`, `query_key`, `scheduler_alias`, `preset`
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_writer_responses` (named `vmanomaly_reader_response_count` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))
+`vmanomaly_model_run_duration_seconds`
+            </td>
+            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)) </td>
+            <td>The total time (in seconds) taken by model invocations during the `stage` (`fit`, `infer`, `fit_infer`), based on the results of the `query_key` query, for models of class `model_alias`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>
+
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
+            </td>
+        </tr>
+        <tr>
+            <td>
+
+`vmanomaly_model_datapoints_accepted`
             </td>
             <td>`Counter`</td>
-            <td>The count of response codes received from VictoriaMetrics `url` for the `query_key` query, categorized by `code`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.
-</td>
+            <td>The number of datapoints accepted (excluding NaN or Inf values) by models of class `model_alias` from the results of the `query_key` query during the `stage` (`infer`, `fit_infer`), within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`url`, `code`, `query_key`, `scheduler_alias`, `preset`
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_writer_sent_bytes`
+`vmanomaly_model_datapoints_produced`
             </td>
             <td>`Counter`</td>
-            <td>The total number of bytes sent to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The number of datapoints generated by models of class `model_alias` during the `stage` (`infer`, `fit_infer`) based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`url`, `query_key`, `scheduler_alias`, `preset`
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_writer_request_serialize_seconds`
+`vmanomaly_models_active`
             </td>
-            <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
-            <td>The total time (in seconds) taken for serializing data for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>`Gauge`</td>
+            <td>The number of model instances of class `model_alias` currently available for inference for the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`query_key`, `scheduler_alias`, `preset`
+`query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_writer_datapoints_sent`
+`vmanomaly_model_runs_skipped`
             </td>
             <td>`Counter`</td>
-            <td>The total number of datapoints sent to VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The number of times model runs (of class `model_alias`) were skipped in expected situations (e.g., no data for fitting/inference, or no new data to infer on) during the `stage` (`fit`, `infer`, `fit_infer`), based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`query_key`, `scheduler_alias`, `preset`
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
-`vmanomaly_writer_timeseries_sent`
+
+`vmanomaly_model_run_errors`
             </td>
             <td>`Counter`</td>
-            <td>The total number of timeseries sent to VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The number of times model runs (of class `model_alias`) failed due to internal service errors during the `stage` (`fit`, `infer`, `fit_infer`), based on results from the `query_key` query, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
-`query_key`, `scheduler_alias`, `preset`
+`stage`, `query_key`, `model_alias`, `scheduler_alias`, `preset`
             </td>
         </tr>
     </tbody>
 </table>
 
-### Reader Behaviour Metrics
+[Back to metric sections](#metrics-generated-by-vmanomaly)
+
+### Writer behaviour metrics
 Label names [description](#labelnames)
 
+> **Note**: additional labels (`scheduler_alias`, `preset`) were added to writer and reader metrics in [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170) to improve consistency across the components. Also, metrics `vmanomaly_writer_request_duration_seconds` and `vmanomaly_writer_request_serialize_seconds` changed their type to `Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170)).
+
 <table class="params">
     <thead>
         <tr>
@@ -455,10 +486,11 @@ Label names [description](#labelnames)
         <tr>
             <td>
 
-`vmanomaly_reader_request_duration_seconds`
+`vmanomaly_writer_request_duration_seconds`
             </td>
             <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
-            <td>The total time (in seconds) taken by queries to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total time (in seconds) taken by write requests to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.
+</td>
             <td>
 
 `url`, `query_key`, `scheduler_alias`, `preset`
@@ -467,46 +499,47 @@ Label names [description](#labelnames)
         <tr>
             <td>
 
-`vmanomaly_reader_responses` (named `vmanomaly_reader_response_count` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))
+`vmanomaly_writer_responses` (named `vmanomaly_reader_response_count` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))
             </td>
             <td>`Counter`</td>
-            <td>The count of responses received from VictoriaMetrics `url` for the `query_key` query, categorized by `code`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The count of response codes received from VictoriaMetrics `url` for the `query_key` query, categorized by `code`, within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.
+</td>
             <td>
 
-`url`, `query_key`, `code`, `scheduler_alias`, `preset`
+`url`, `code`, `query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_reader_received_bytes`
+`vmanomaly_writer_sent_bytes`
             </td>
             <td>`Counter`</td>
-            <td>The total number of bytes received in responses for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of bytes sent to VictoriaMetrics `url` for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`query_key`, `scheduler_alias`, `preset`
+`url`, `query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_reader_response_parsing_seconds`
+`vmanomaly_writer_request_serialize_seconds`
             </td>
             <td>`Histogram` (was `Summary` prior to [v1.17.0](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1170))</td>
-            <td>The total time (in seconds) taken for data parsing at each `step` (json, dataframe) for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total time (in seconds) taken for serializing data for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
-`step`, `query_key`, `scheduler_alias`, `preset`
+`query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
         <tr>
             <td>
 
-`vmanomaly_reader_timeseries_received`
+`vmanomaly_writer_datapoints_sent`
             </td>
             <td>`Counter`</td>
-            <td>The total number of timeseries received from VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of datapoints sent to VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
 
 `query_key`, `scheduler_alias`, `preset`
@@ -514,19 +547,19 @@ Label names [description](#labelnames)
         </tr>
         <tr>
             <td>
-
-`vmanomaly_reader_datapoints_received`
+`vmanomaly_writer_timeseries_sent`
             </td>
             <td>`Counter`</td>
-            <td>The total number of datapoints received from VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
+            <td>The total number of timeseries sent to VictoriaMetrics for the `query_key` query within the specified scheduler `scheduler_alias`, in the `vmanomaly` service running in `preset` mode.</td>
             <td>
-
 `query_key`, `scheduler_alias`, `preset`
             </td>
         </tr>
     </tbody>
 </table>
 
+[Back to metric sections](#metrics-generated-by-vmanomaly)
+
 ### Labelnames
 
 * `stage` - stage of model - 'fit', 'infer' or 'fit_infer' for models that do it simultaneously, see [model types](https://docs.victoriametrics.com/anomaly-detection/components/models/#model-types).
@@ -537,3 +570,312 @@ Label names [description](#labelnames)
 * `url` - writer or reader url endpoint.
 * `code` - response status code or `connection_error`, `timeout`.
 * `step` - json or dataframe reading step.
+
+[Back to metric sections](#metrics-generated-by-vmanomaly)
+
+
+## Logs generated by vmanomaly
+
+The `vmanomaly` service logs operations, errors, and performance for its components (service, reader, writer), alongside [self-monitoring metrics](#metrics-generated-by-vmanomaly) updates. Below is a description of key logs for each component and the related metrics affected.
+
+`{{X}}` indicates a placeholder in the log message templates described below, which will be replaced with the appropriate entity during logging.
+
+
+> **Note**: Applicable to version [v1.17.1](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1171) or newer.
+
+> **Note**: By default, `vmanomaly` uses the `INFO` logging level. You can change this by specifying the `--loggerLevel` argument. See command-line arguments [here](https://docs.victoriametrics.com/anomaly-detection/quickstart/#command-line-arguments).
+
+- [Startup logs](#startup-logs)
+- [Reader  logs](#reader-logs)
+- [Service logs](#service-logs)
+- [Writer  logs](#writer-logs)
+
+
+### Startup logs
+
+The `vmanomaly` service logs important information during the startup process. This includes checking for the license, validating configurations, and setting up schedulers, readers, and writers. Below are key logs that are generated during startup, which can help troubleshoot issues with the service's initial configuration or license validation.
+
+---
+
+**License check**. If no license key or file is provided, the service will fail to start and log an error message. If a license file is provided but cannot be read, the service logs a failure. Log messages:
+
+```text
+Please provide a license code using --license or --licenseFile arg, or as VM_LICENSE_FILE env. See https://victoriametrics.com/products/enterprise/trial/ to obtain a trial license.
+```
+
+```text
+failed to read file {{args.license_file}}: {{error_message}}
+```
+
+---
+
+**Config validation**. If the service's configuration fails to load or does not meet validation requirements, an error message is logged and the service will exit. If the configuration is loaded successfully, a message confirming the successful load is logged. Log messages:
+
+```text
+Config validation failed, please fix these errors: {{error_details}}
+```
+
+```text
+Config has been loaded successfully.
+```
+
+---
+
+**Model and data directory setup**. The service checks the environment variables `VMANOMALY_MODEL_DUMPS_DIR` and `VMANOMALY_DATA_DUMPS_DIR` to determine where to store models and data. If these variables are not set, models and data will be stored in memory. Please find the [on-disk mode details here](https://docs.victoriametrics.com/anomaly-detection/faq/#on-disk-mode). Log messages:
+
+```text
+Using ENV MODEL_DUMP_DIR=`{{model_dump_dir}}` to store anomaly detection models.
+```
+```text
+ENV MODEL_DUMP_DIR is not set. Models will be kept in RAM between consecutive `fit` calls.
+```
+```text
+Using ENV DATA_DUMP_DIR=`{{data_dump_dir}}` to store anomaly detection data.
+```
+```text
+ENV DATA_DUMP_DIR is not set. Models' training data will be stored in RAM.
+```
+
+---
+
+**Scheduler and service initialization**. After configuration is successfully loaded, the service initializes [schedulers](https://docs.victoriametrics.com/anomaly-detection/components/scheduler/) and services for each defined `scheduler_alias`. If there are issues with a specific scheduler (e.g., no models or queries found to attach to a scheduler), a warning is logged. When schedulers are initialized, the service logs a list of active schedulers. Log messages:
+
+```text
+Scheduler {{scheduler_alias}} wrapped and initialized with {{N}} model spec(s).
+```
+```text
+No model spec(s) found for scheduler `{{scheduler_alias}}`, skipping setting it up.
+```
+```text
+Active schedulers: {{list_of_schedulers}}.
+```
+
+[Back to logging sections](#logs-generated-by-vmanomaly)
+
+---
+
+### Reader logs
+
+The `reader` component logs events during the process of querying VictoriaMetrics and retrieving the data necessary for anomaly detection. This includes making HTTP requests, handling SSL, parsing responses, and processing data into formats like DataFrames. The logs help to troubleshoot issues such as connection problems, timeout errors, or misconfigured queries.
+
+---
+
+**Starting a healthcheck request**. When the `reader` component initializes, it checks whether the VictoriaMetrics endpoint is accessible by sending a request for `_vmanomaly_healthcheck`. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] Max points per timeseries set as: {{vm_max_datapoints_per_ts}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Reader endpoint SSL error {{url}}: {{error_message}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Reader endpoint inaccessible {{url}}: {{error_message}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Reader endpoint timeout {{url}}: {{error_message}}
+```
+
+---
+
+
+**No data found (False)**. Based on [`query_from_last_seen_timestamp`](https://docs.victoriametrics.com/anomaly-detection/components/reader/?highlight=query_from_last_seen_timestamp#config-parameters) VmReader flag. A `warning` log is generated when no data is found in the requested range. This could indicate that the query was misconfigured or that no new data exists for the time period requested. Log message format:
+
+```text
+[Scheduler {{scheduler_alias}}] No data between {{start_s}} and {{end_s}} for query "{{query_key}}"
+```
+
+---
+
+**No unseen data found (True)**. Based on [`query_from_last_seen_timestamp`](https://docs.victoriametrics.com/anomaly-detection/components/reader/?highlight=query_from_last_seen_timestamp#config-parameters) VmReader flag. A `warning` log is generated when no new data is returned (i.e., all data has already been seen in a previous inference step(s)). This helps in identifying situations where data for inference has already been processed. Based on VmReader's `adjust` flag. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] No unseen data between {{start_s}} and {{end_s}} for query "{{query_key}}"
+```
+
+---
+
+**Connection or timeout errors**. When the reader fails to retrieve data due to connection or timeout errors, a `warning` log is generated. These errors could result from network issues, incorrect query endpoints, or VictoriaMetrics being temporarily unavailable. Log message format:
+
+```text
+[Scheduler {{scheduler_alias}}] Error querying {{query_key}} for {{url}}: {{error_message}}
+```
+
+---
+
+**Max datapoints warning**. If the requested query range (defined by `fit_every` or `infer_every` [scheduler](https://docs.victoriametrics.com/anomaly-detection/components/scheduler/#parameters-1) args) exceeds the maximum number of datapoints allowed by VictoriaMetrics, a `warning` log is generated, and the request is split into multiple intervals (option available since [v1.14.1](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1141)). This ensures that the request does not violate VictoriaMetrics’ constraints. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] Query "{{query_key}}" from {{start_s}} to {{end_s}} with step {{step}} may exceed max datapoints per timeseries and will be split...
+```
+
+---
+
+**Multi-tenancy warnings**. If the reader detects any issues related to missing or misconfigured multi-tenancy labels (supported since [v1.16.2](https://docs.victoriametrics.com/anomaly-detection/changelog/index.html#v1162)), a `warning` log is generated to indicate the issue. See additional details [here](https://docs.victoriametrics.com/anomaly-detection/components/writer/#multitenancy-support). Log message format:
+
+```text
+The label vm_account_id was not found in the label set of {{query_key}}, but tenant_id='multitenant' is set in reader configuration...
+```
+
+---
+
+**Metrics updated in read operations**. During successful query execution process, the following reader [self-monitoring metrics](#reader-behaviour-metrics) are updated:
+
+- `vmanomaly_reader_request_duration_seconds`: Records the time (in seconds) taken to complete the query request.
+  
+- `vmanomaly_reader_responses`: Tracks the number of response codes received from VictoriaMetrics.
+
+- `vmanomaly_reader_received_bytes`: Counts the number of bytes received in the response.
+
+- `vmanomaly_reader_response_parsing_seconds`: Records the time spent parsing the response into different formats (e.g., JSON or DataFrame).
+
+- `vmanomaly_reader_timeseries_received`: Tracks how many timeseries were retrieved in the query result.
+
+- `vmanomaly_reader_datapoints_received`: Counts the number of datapoints retrieved in the query result.
+
+---
+
+**Metrics skipped in case of failures**. If an error occurs (connection or timeout), `vmanomaly_reader_received_bytes`, `vmanomaly_reader_timeseries_received`, and `vmanomaly_reader_datapoints_received` are not incremented because no valid data was received.
+
+[Back to logging sections](#logs-generated-by-vmanomaly)
+
+### Service logs
+
+The `model` component (wrapped in service) logs operations during the fitting and inference stages for each model spec attached to particular [scheduler](https://docs.victoriametrics.com/anomaly-detection/components/scheduler/) `scheduler_alias`. These logs inform about skipped runs, connection or timeout issues, invalid data points, and successful or failed model operations.
+
+---
+
+**Skipped runs**. When there are insufficient valid data points to fit or infer using a model, the run is skipped and a `warning` log is generated. This can occur when the query returns no new data or when the data contains invalid values (e.g., `NaN`, `INF`). The skipped run is also reflected in the `vmanomaly_model_runs_skipped` metric. Log messages:
+
+When there are insufficient valid data points (at least 1 for [online models](https://docs.victoriametrics.com/anomaly-detection/components/models#online-models) and 2 for [offline models](https://docs.victoriametrics.com/anomaly-detection/components/models#offline-models))
+```text
+[Scheduler {{scheduler_alias}}] Skipping run for stage 'fit' for model '{{model_alias}}' (query_key: {{query_key}}): Not enough valid data to fit: {{valid_values_cnt}}
+```
+
+When all the received timestamps during an `infer` call have already been processed, meaning the [`anomaly_score`](https://docs.victoriametrics.com/anomaly-detection/faq/index.html#what-is-anomaly-score) has already been produced for those points
+```text
+[Scheduler {{scheduler_alias}}] Skipping run for stage 'infer' for model '{{model_alias}}' (query_key: {{query_key}}): No unseen data to infer on.
+```
+When the model fails to produce any valid or finite outputs (such as [`anomaly_score`](https://docs.victoriametrics.com/anomaly-detection/faq/index.html#what-is-anomaly-score))
+```text
+[Scheduler {{scheduler_alias}}] Skipping run for stage 'infer' for model '{{model_alias}}' (query_key: {{query_key}}): No (valid) datapoints produced.
+```
+
+---
+
+**Errors during model execution**. If the model fails to fit or infer data due to internal service errors or model spec misconfigurations, an `error` log is generated and the error is also reflected in the `vmanomaly_model_run_errors` metric. This can occur during both `fit` and `infer` stages. Log messages:
+```text
+[Scheduler {{scheduler_alias}}] Error during stage 'fit' for model '{{model_alias}}' (query_key: {{query_key}}): {{error_message}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Error during stage 'infer' for model '{{model_alias}}' (query_key: {{query_key}}): {{error_message}}
+```
+
+---
+
+**Model instance created during inference**. In cases where an [online model](https://docs.victoriametrics.com/anomaly-detection/components/models#online-models) instance is created during the inference stage (without a prior fit, a feature introduced in [v1.15.2](https://docs.victoriametrics.com/anomaly-detection/changelog/#v1152)), a `debug` log is produced. This helps track models that are created dynamically based on incoming data. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] Model instance '{{model_alias}}' created for '{{query_key}}' during inference.
+```
+---
+
+**Successful model runs**. When a model successfully fits, logs track the number of valid datapoints processed and the time taken for the operation. These logs are accompanied by updates to [self-monitoring metrics](#models-behaviour-metrics) like `vmanomaly_model_runs`, `vmanomaly_model_run_duration_seconds`, `vmanomaly_model_datapoints_accepted`, and `vmanomaly_model_datapoints_produced`. Log messages:
+
+For [non-rolling models](https://docs.victoriametrics.com/anomaly-detection/components/models/#non-rolling-models)
+```text
+[Scheduler {{scheduler_alias}}] Fitting on {{valid_values_cnt}}/{{total_values_cnt}} valid datapoints for "{{query_key}}" using model "{{model_alias}}".
+```
+```text
+[Scheduler {{scheduler_alias}}] Model '{{model_alias}}' fit completed in {{model_run_duration}} seconds for {{query_key}}.
+```
+For [rolling models](https://docs.victoriametrics.com/anomaly-detection/components/models/#rolling-models) (combined stage)
+```text
+[Scheduler {{scheduler_alias}}] Fit-Infer on {{datapoint_count}} points for "{{query_key}}" using model "{{model_alias}}".
+```
+
+---
+
+**Metrics updated in model runs**. During successful fit or infer operations, the following [self-monitoring metrics](#models-behaviour-metrics) are updated for each run:
+
+- `vmanomaly_model_runs`: Tracks how many times the model ran (`fit`, `infer`, or `fit_infer`) for a specific `query_key`.
+
+- `vmanomaly_model_run_duration_seconds`: Records the total time (in seconds) for the model invocation, based on the results of the `query_key`.
+
+- `vmanomaly_model_datapoints_accepted`: The number of valid datapoints processed by the model during the run.
+
+- `vmanomaly_model_datapoints_produced`: The number of datapoints generated by the model during inference.
+
+- `vmanomaly_models_active`: Tracks the number of models currently **available for infer** for a specific `query_key`.
+
+---
+
+**Metrics skipped in case of failures**. If a model run fails due to an error or if no valid data is available, the metrics such as `vmanomaly_model_datapoints_accepted`, `vmanomaly_model_datapoints_produced`, and `vmanomaly_model_run_duration_seconds` are not updated.
+
+---
+
+[Back to logging sections](#logs-generated-by-vmanomaly)
+
+### Writer logs
+
+The `writer` component logs events during the process of sending produced data (like `anomaly_score` [metrics](https://docs.victoriametrics.com/anomaly-detection/faq/index.html#what-is-anomaly-score)) to VictoriaMetrics. This includes data preparation, serialization, and network requests to VictoriaMetrics endpoints. The logs can help identify issues in data transmission, such as connection errors, invalid data points, and track the performance of write requests.
+
+---
+
+**Starting a write request**. A `debug` level log is produced when the `writer` component starts the process of writing data to VictoriaMetrics. It includes details like the number of datapoints, bytes of payload, and the query being written. This is useful for tracking the payload size and performance at the start of the request. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] POST {{url}} with {{N}} datapoints, {{M}} bytes of payload, for {{query_key}}
+```
+
+---
+
+**No valid data points**. A `warning` log is generated if there are no valid datapoints to write (i.e., all are `NaN` or unsupported like `INF`). This indicates that the writer will not send any data to VictoriaMetrics. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] No valid datapoints to save for metric: {{query_key}}
+```
+
+---
+
+**Connection, timeout, or I/O errors**. When the writer fails to send data due to connection, timeout, or I/O errors, an `error` log is generated. These errors often arise from network problems, incorrect URLs, or VictoriaMetrics being unavailable. The log includes details of the failed request and the reason for the failure. Log messages:
+
+```text
+[Scheduler {{scheduler_alias}}] Cannot write {{N}} points for {{query_key}}: connection error {{url}} {{error_message}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Cannot write {{N}} points for {{query_key}}: timeout for {{url}} {{error_message}}
+```
+```text
+[Scheduler {{scheduler_alias}}] Cannot write {{N}} points for {{query_key}}: I/O error for {{url}} {{error_message}}
+```
+
+---
+
+**Multi-tenancy warnings**. If the `tenant_id` is set to `multitenant` but the `vm_account_id` label is missing from the query result, or vice versa, a `warning` log is produced (supported since [v1.16.2](https://docs.victoriametrics.com/anomaly-detection/changelog/index.html#v1162)). This helps in debugging label set issues that may occur due to the multi-tenant configuration - see [this section for details](https://docs.victoriametrics.com/anomaly-detection/components/writer/#multitenancy-support). Log messages:
+
+```text
+The label vm_account_id was not found in the label set of {{query_key}}, but tenant_id='multitenant' is set in writer...
+```
+```text
+The label set for the metric {{query_key}} contains multi-tenancy labels, but the write endpoint is configured for single-tenant mode (tenant_id != 'multitenant')...
+```
+
+---
+
+**Metrics updated in write operations**. During the successful write process of *non-empty data*, the following [self-monitoring metrics](#writer-behaviour-metrics) are updated:
+
+- `vmanomaly_writer_request_duration_seconds`: Records the time (in seconds) taken to complete the write request.
+
+- `vmanomaly_writer_sent_bytes`: Tracks the number of bytes sent in the request.
+
+- `vmanomaly_writer_responses`: Captures the HTTP response code returned by VictoriaMetrics. In case of connection, timeout, or I/O errors, a specific error code (`connection_error`, `timeout`, or `io_error`) is recorded instead.
+
+- `vmanomaly_writer_request_serialize_seconds`: Records the time taken for data serialization.
+
+- `vmanomaly_writer_datapoints_sent`: Counts the number of valid datapoints that were successfully sent.
+
+- `vmanomaly_writer_timeseries_sent`: Tracks the number of timeseries sent to VictoriaMetrics.
+
+**Metrics skipped in case of failures**. If an error occurs (connection, timeout, or I/O error), only `vmanomaly_writer_request_duration_seconds` is updated with appropriate error code. 
+
+[Back to logging sections](#logs-generated-by-vmanomaly)
diff --git a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md
index 09cff8d90..610abd511 100644
--- a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md
+++ b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md
@@ -385,7 +385,7 @@ services:
     restart: always
   vmanomaly:
     container_name: vmanomaly
-    image: victoriametrics/vmanomaly:v1.17.1
+    image: victoriametrics/vmanomaly:v1.17.2
     depends_on:
       - "victoriametrics"
     ports:
diff --git a/docs/changelog/CHANGELOG.md b/docs/changelog/CHANGELOG.md
index 4dfc658a7..50d3fb9cf 100644
--- a/docs/changelog/CHANGELOG.md
+++ b/docs/changelog/CHANGELOG.md
@@ -18,6 +18,8 @@ See also [LTS releases](https://docs.victoriametrics.com/lts-releases/).
 
 ## tip
 
+* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert): properly set `group_name` and `file` fields for recording rules in `/api/v1/rules`.
+
 ## [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
 
 Released at 2024-10-21
diff --git a/docs/helm/victoria-logs-single/CHANGELOG.md b/docs/helm/victoria-logs-single/CHANGELOG.md
index 2b0975302..c1d1504c1 100644
--- a/docs/helm/victoria-logs-single/CHANGELOG.md
+++ b/docs/helm/victoria-logs-single/CHANGELOG.md
@@ -1,6 +1,6 @@
 ## Next release
 
-- TODO
+- Custom fluent-bit template to push data to multiple VLogs instances when replica count is greated than 1.
 
 ## 0.6.6
 
diff --git a/docs/helm/victoria-logs-single/README.md b/docs/helm/victoria-logs-single/README.md
index a83361181..1a0dcd634 100644
--- a/docs/helm/victoria-logs-single/README.md
+++ b/docs/helm/victoria-logs-single/README.md
@@ -175,26 +175,15 @@ Change the values according to the need of the environment in ``victoria-logs-si
             Nested_under kubernetes
             Add_prefix   kubernetes_
     outputs: |
-        [OUTPUT]
-            Name             http
-            Match            kube.*
-            Host             {{ include "victoria-logs.server.fullname" . }}
-            port             9428
-            compress         gzip
-            uri              /insert/jsonline
-            format           json_lines
-            json_date_format iso8601
-            header           AccountID 0
-            header           ProjectID 0
-            header           VL-Msg-Field log
-            header           VL-Time-Field date
-            header           VL-Stream-Fields stream,kubernetes_pod_name,kubernetes_container_name,kubernetes_namespace_name
+        @INCLUDE /fluent-bit/etc/conf/vl/output_*.conf
 daemonSetVolumeMounts:
     - mountPath: /var/log
       name: varlog
     - mountPath: /var/lib/docker/containers
       name: varlibdockercontainers
       readOnly: true
+    - mountPath: /fluent-bit/etc/conf/vl
+      name: victorialogs-outputs
 daemonSetVolumes:
     - hostPath:
         path: /var/log
@@ -202,6 +191,9 @@ daemonSetVolumes:
     - hostPath:
         path: /var/lib/docker/containers
       name: varlibdockercontainers
+    - configMap:
+        name: victorialogs-outputs
+      name: victorialogs-outputs
 enabled: false
 resources: {}
 </code>
@@ -241,20 +233,7 @@ resources: {}
       <td>tpl</td>
       <td><pre class="helm-vars-default-value" language-yaml" lang="tpl">
 <code class="language-yaml">fluent-bit.config.outputs: |
-  [OUTPUT]
-      Name             http
-      Match            kube.*
-      Host             {{ include "victoria-logs.server.fullname" . }}
-      port             9428
-      compress         gzip
-      uri              /insert/jsonline
-      format           json_lines
-      json_date_format iso8601
-      header           AccountID 0
-      header           ProjectID 0
-      header           VL-Msg-Field log
-      header           VL-Time-Field date
-      header           VL-Stream-Fields stream,kubernetes_pod_name,kubernetes_container_name,kubernetes_namespace_name
+  @INCLUDE /fluent-bit/etc/conf/vl/output_*.conf
  
 </code>
 </pre>
@@ -316,28 +295,6 @@ resources: {}
 </pre>
 </td>
       <td><p>Global name override</p>
-</td>
-    </tr>
-    <tr>
-      <td>global.victoriaLogs.server.fullnameOverride</td>
-      <td>string</td>
-      <td><pre class="helm-vars-default-value" language-yaml" lang="">
-<code class="language-yaml">null
-</code>
-</pre>
-</td>
-      <td><p>Overrides the full name of server component</p>
-</td>
-    </tr>
-    <tr>
-      <td>global.victoriaLogs.server.name</td>
-      <td>string</td>
-      <td><pre class="helm-vars-default-value" language-yaml" lang="">
-<code class="language-yaml">server
-</code>
-</pre>
-</td>
-      <td><p>Server container name</p>
 </td>
     </tr>
     <tr>
diff --git a/docs/helm/victoria-metrics-agent/CHANGELOG.md b/docs/helm/victoria-metrics-agent/CHANGELOG.md
index 89526a454..5def3c0f6 100644
--- a/docs/helm/victoria-metrics-agent/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-agent/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.14.3
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.14.2
 
 **Release date:** 2024-10-11
diff --git a/docs/helm/victoria-metrics-agent/README.md b/docs/helm/victoria-metrics-agent/README.md
index 674b178ee..74733c3d0 100644
--- a/docs/helm/victoria-metrics-agent/README.md
+++ b/docs/helm/victoria-metrics-agent/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.14.2](https://img.shields.io/badge/Version-0.14.2-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.14.3](https://img.shields.io/badge/Version-0.14.3-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-agent)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-alert/CHANGELOG.md b/docs/helm/victoria-metrics-alert/CHANGELOG.md
index a83f248bd..5ef621af6 100644
--- a/docs/helm/victoria-metrics-alert/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-alert/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.12.3
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.12.2
 
 **Release date:** 2024-10-11
diff --git a/docs/helm/victoria-metrics-alert/README.md b/docs/helm/victoria-metrics-alert/README.md
index aed4e209c..c1d27ab0b 100644
--- a/docs/helm/victoria-metrics-alert/README.md
+++ b/docs/helm/victoria-metrics-alert/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.12.2](https://img.shields.io/badge/Version-0.12.2-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.12.3](https://img.shields.io/badge/Version-0.12.3-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-alert)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-auth/CHANGELOG.md b/docs/helm/victoria-metrics-auth/CHANGELOG.md
index ae2c4ca19..8edcd95db 100644
--- a/docs/helm/victoria-metrics-auth/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-auth/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.7.3
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.7.2
 
 **Release date:** 2024-10-11
diff --git a/docs/helm/victoria-metrics-auth/README.md b/docs/helm/victoria-metrics-auth/README.md
index dd48bca47..9d12c7b84 100644
--- a/docs/helm/victoria-metrics-auth/README.md
+++ b/docs/helm/victoria-metrics-auth/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.7.2](https://img.shields.io/badge/Version-0.7.2-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.7.3](https://img.shields.io/badge/Version-0.7.3-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-auth)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-cluster/CHANGELOG.md b/docs/helm/victoria-metrics-cluster/CHANGELOG.md
index 413b6edcb..ce463b254 100644
--- a/docs/helm/victoria-metrics-cluster/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-cluster/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.14.6
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.14.5
 
 **Release date:** 2024-10-18
diff --git a/docs/helm/victoria-metrics-cluster/README.md b/docs/helm/victoria-metrics-cluster/README.md
index 5c3c140c7..05e6eba2b 100644
--- a/docs/helm/victoria-metrics-cluster/README.md
+++ b/docs/helm/victoria-metrics-cluster/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.14.5](https://img.shields.io/badge/Version-0.14.5-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.14.6](https://img.shields.io/badge/Version-0.14.6-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-cluster)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-distributed/CHANGELOG.md b/docs/helm/victoria-metrics-distributed/CHANGELOG.md
index 3f34b6ae7..68e385b4c 100644
--- a/docs/helm/victoria-metrics-distributed/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-distributed/CHANGELOG.md
@@ -1,6 +1,16 @@
 ## Next release
 
+- TODO
+
+## 0.4.1
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
 - Human-readable error about Helm version requirement
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
 
 ## 0.4.0
 
diff --git a/docs/helm/victoria-metrics-distributed/README.md b/docs/helm/victoria-metrics-distributed/README.md
index 10adaf973..3a17821e4 100644
--- a/docs/helm/victoria-metrics-distributed/README.md
+++ b/docs/helm/victoria-metrics-distributed/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.4.0](https://img.shields.io/badge/Version-0.4.0-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.4.1](https://img.shields.io/badge/Version-0.4.1-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-distributed)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-gateway/CHANGELOG.md b/docs/helm/victoria-metrics-gateway/CHANGELOG.md
index c1b6d6bee..24dfc676b 100644
--- a/docs/helm/victoria-metrics-gateway/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-gateway/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.5.3
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.5.2
 
 **Release date:** 2024-10-11
diff --git a/docs/helm/victoria-metrics-gateway/README.md b/docs/helm/victoria-metrics-gateway/README.md
index dc9861fcc..2def47ea7 100644
--- a/docs/helm/victoria-metrics-gateway/README.md
+++ b/docs/helm/victoria-metrics-gateway/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.5.2](https://img.shields.io/badge/Version-0.5.2-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.5.3](https://img.shields.io/badge/Version-0.5.3-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-gateway)
 [![Slack](https://img.shields.io/badge/join%20slack-%23victoriametrics-brightgreen.svg)](https://slack.victoriametrics.com/)
 
diff --git a/docs/helm/victoria-metrics-k8s-stack/CHANGELOG.md b/docs/helm/victoria-metrics-k8s-stack/CHANGELOG.md
index 7889fdd35..b4d2d9bb4 100644
--- a/docs/helm/victoria-metrics-k8s-stack/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-k8s-stack/CHANGELOG.md
@@ -1,6 +1,16 @@
 ## Next release
 
+- TODO
+
+## 0.27.6
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
 - Add an explicit fail in case both Grafana dashboard via sidecar and `grafana.dashboards` are enabled. Previously, this configuration would be accepted and sidecar configuration would silently override `.grafana.dashboards` configuration. See [these docs](https://docs.victoriametrics.com/helm/victoriametrics-k8s-stack/#adding-external-dashboards) for information about adding external dashboards.
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
 
 ## 0.27.5
 
diff --git a/docs/helm/victoria-metrics-k8s-stack/README.md b/docs/helm/victoria-metrics-k8s-stack/README.md
index fb51a8046..8be2e1bf7 100644
--- a/docs/helm/victoria-metrics-k8s-stack/README.md
+++ b/docs/helm/victoria-metrics-k8s-stack/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.27.5](https://img.shields.io/badge/Version-0.27.5-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.27.6](https://img.shields.io/badge/Version-0.27.6-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-k8s-stack)
 
 Kubernetes monitoring on VictoriaMetrics stack. Includes VictoriaMetrics Operator, Grafana dashboards, ServiceScrapes and VMRules
diff --git a/docs/helm/victoria-metrics-single/CHANGELOG.md b/docs/helm/victoria-metrics-single/CHANGELOG.md
index 17cad4661..aa1cf9179 100644
--- a/docs/helm/victoria-metrics-single/CHANGELOG.md
+++ b/docs/helm/victoria-metrics-single/CHANGELOG.md
@@ -2,6 +2,15 @@
 
 - TODO
 
+## 0.12.3
+
+**Release date:** 2024-10-21
+
+![AppVersion: v1.105.0](https://img.shields.io/static/v1?label=AppVersion&message=v1.105.0&color=success&logo=)
+![Helm: v3](https://img.shields.io/static/v1?label=Helm&message=v3&color=informational&logo=helm)
+
+- bump version of VM components to [v1.105.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.105.0)
+
 ## 0.12.2
 
 **Release date:** 2024-10-11
diff --git a/docs/helm/victoria-metrics-single/README.md b/docs/helm/victoria-metrics-single/README.md
index 38a708cff..fb73d7a1d 100644
--- a/docs/helm/victoria-metrics-single/README.md
+++ b/docs/helm/victoria-metrics-single/README.md
@@ -1,4 +1,4 @@
-![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.12.2](https://img.shields.io/badge/Version-0.12.2-informational?style=flat-square)
+![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![Version: 0.12.3](https://img.shields.io/badge/Version-0.12.3-informational?style=flat-square)
 [![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/victoriametrics)](https://artifacthub.io/packages/helm/victoriametrics/victoria-metrics-single)
 
 Victoria Metrics Single version - high-performance, cost-effective and scalable TSDB, long-term remote storage for Prometheus
diff --git a/docs/operator/CHANGELOG.md b/docs/operator/CHANGELOG.md
index 44f8be24e..d931e2ad8 100644
--- a/docs/operator/CHANGELOG.md
+++ b/docs/operator/CHANGELOG.md
@@ -11,7 +11,13 @@ aliases:
   - /operator/changelog/index.html
 ---
 
+## [v0.48.4](https://github.com/VictoriaMetrics/operator/releases/tag/v0.48.4) - 15 Oct 2024
+
+- [api](https://docs.victoriametrics.com/operator/api): adds new fields `maxDiskUsagePerUrl` and`forceVMProto` to the `VMagent` `remoteWriteSpec`
 - [vmuser](https://docs.victoriametrics.com/operator/resources/vmuser/): fixes the protocol of generated CRD target access url for vminsert and vmstorage when TLS is enabled.
+- [vmagent](https://docs.victoriametrics.com/operator/resources/vmagent/): properly make transition to `statefulMode`. See [this issue](https://github.com/VictoriaMetrics/operator/issues/1127) for details.
+- [vmagent](https://docs.victoriametrics.com/operator/resources/vmagent/): properly assign `OwnerRefrence` for `Role` and `RoleBinding` at `single-namespace` operator mode.
+- [operator](https://docs.victoriametrics.com/operator/): fixes pod scheduling with `useStrictSecurity` enabled by removing default values for `AppArmorProfile` and `SeccompProfile`. See [this issue](https://github.com/VictoriaMetrics/operator/issues/1120) for details.
 
 ## [v0.48.3](https://github.com/VictoriaMetrics/operator/releases/tag/v0.48.3) - 29 Sep 2024
 
diff --git a/docs/operator/api.md b/docs/operator/api.md
index 437e34d29..206db8363 100644
--- a/docs/operator/api.md
+++ b/docs/operator/api.md
@@ -2518,8 +2518,10 @@ _Appears in:_
 | --- | --- | --- | --- |
 | `basicAuth` | BasicAuth allow an endpoint to authenticate over basic authentication | _[BasicAuth](#basicauth)_ | false |
 | `bearerTokenSecret` | Optional bearer auth token to use for -remoteWrite.url | _[SecretKeySelector](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.30/#secretkeyselector-v1-core)_ | false |
+| `forceVMProto` | ForceVMProto forces using VictoriaMetrics protocol for sending data to -remoteWrite.url | _boolean_ | false |
 | `headers` | Headers allow configuring custom http headers<br />Must be in form of semicolon separated header with value<br />e.g.<br />headerName: headerValue<br />vmagent supports since 1.79.0 version | _string array_ | false |
 | `inlineUrlRelabelConfig` | InlineUrlRelabelConfig defines relabeling config for remoteWriteURL, it can be defined at crd spec. | _[RelabelConfig](#relabelconfig) array_ | false |
+| `maxDiskUsage` | MaxDiskUsage defines the maximum file-based buffer size in bytes for -remoteWrite.url | _string_ | false |
 | `oauth2` | OAuth2 defines auth configuration | _[OAuth2](#oauth2)_ | false |
 | `sendTimeout` | Timeout for sending a single block of data to -remoteWrite.url (default 1m0s) | _string_ | false |
 | `streamAggrConfig` | StreamAggrConfig defines stream aggregation configuration for VMAgent for -remoteWrite.url | _[StreamAggrConfig](#streamaggrconfig)_ | false |
diff --git a/docs/operator/vars.md b/docs/operator/vars.md
index b24d4370d..8a70c0703 100644
--- a/docs/operator/vars.md
+++ b/docs/operator/vars.md
@@ -10,7 +10,7 @@ aliases:
   - /operator/vars/index.html
 ---
 <!-- this doc autogenerated - don't edit it manually -->
- updated at Mon Oct  7 04:29:16 UTC 2024
+ updated at Mon Oct 21 21:47:16 UTC 2024
 
 
 | variable name | variable default value | variable required | variable description |
@@ -31,7 +31,7 @@ aliases:
 | VM_VLOGSDEFAULT_CONFIGRELOADERCPU | - | false | ignored |
 | VM_VLOGSDEFAULT_CONFIGRELOADERMEMORY | - | false | ignored |
 | VM_VMALERTDEFAULT_IMAGE | victoriametrics/vmalert | false | - |
-| VM_VMALERTDEFAULT_VERSION | v1.104.0 | false | - |
+| VM_VMALERTDEFAULT_VERSION | v1.105.0 | false | - |
 | VM_VMALERTDEFAULT_CONFIGRELOADIMAGE | jimmidyson/configmap-reload:v0.3.0 | false | - |
 | VM_VMALERTDEFAULT_PORT | 8080 | false | - |
 | VM_VMALERTDEFAULT_USEDEFAULTRESOURCES | true | false | - |
@@ -42,7 +42,7 @@ aliases:
 | VM_VMALERTDEFAULT_CONFIGRELOADERCPU | 100m | false | - |
 | VM_VMALERTDEFAULT_CONFIGRELOADERMEMORY | 25Mi | false | - |
 | VM_VMAGENTDEFAULT_IMAGE | victoriametrics/vmagent | false | - |
-| VM_VMAGENTDEFAULT_VERSION | v1.104.0 | false | - |
+| VM_VMAGENTDEFAULT_VERSION | v1.105.0 | false | - |
 | VM_VMAGENTDEFAULT_CONFIGRELOADIMAGE | quay.io/prometheus-operator/prometheus-config-reloader:v0.68.0 | false | - |
 | VM_VMAGENTDEFAULT_PORT | 8429 | false | - |
 | VM_VMAGENTDEFAULT_USEDEFAULTRESOURCES | true | false | - |
@@ -53,7 +53,7 @@ aliases:
 | VM_VMAGENTDEFAULT_CONFIGRELOADERCPU | 100m | false | - |
 | VM_VMAGENTDEFAULT_CONFIGRELOADERMEMORY | 25Mi | false | - |
 | VM_VMSINGLEDEFAULT_IMAGE | victoriametrics/victoria-metrics | false | - |
-| VM_VMSINGLEDEFAULT_VERSION | v1.104.0 | false | - |
+| VM_VMSINGLEDEFAULT_VERSION | v1.105.0 | false | - |
 | VM_VMSINGLEDEFAULT_CONFIGRELOADIMAGE | - | false | ignored |
 | VM_VMSINGLEDEFAULT_PORT | 8429 | false | - |
 | VM_VMSINGLEDEFAULT_USEDEFAULTRESOURCES | true | false | - |
@@ -65,14 +65,14 @@ aliases:
 | VM_VMSINGLEDEFAULT_CONFIGRELOADERMEMORY | - | false | ignored |
 | VM_VMCLUSTERDEFAULT_USEDEFAULTRESOURCES | true | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_IMAGE | victoriametrics/vmselect | false | - |
-| VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_VERSION | v1.104.0-cluster | false | - |
+| VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_VERSION | v1.105.0-cluster | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_PORT | 8481 | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_RESOURCE_LIMIT_MEM | 1000Mi | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_RESOURCE_LIMIT_CPU | 500m | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_RESOURCE_REQUEST_MEM | 500Mi | false | - |
 | VM_VMCLUSTERDEFAULT_VMSELECTDEFAULT_RESOURCE_REQUEST_CPU | 100m | false | - |
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_IMAGE | victoriametrics/vmstorage | false | - |
-| VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_VERSION | v1.104.0-cluster | false | - |
+| VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_VERSION | v1.105.0-cluster | false | - |
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_VMINSERTPORT | 8400 | false | - |
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_VMSELECTPORT | 8401 | false | - |
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_PORT | 8482 | false | - |
@@ -81,7 +81,7 @@ aliases:
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_RESOURCE_REQUEST_MEM | 500Mi | false | - |
 | VM_VMCLUSTERDEFAULT_VMSTORAGEDEFAULT_RESOURCE_REQUEST_CPU | 250m | false | - |
 | VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_IMAGE | victoriametrics/vminsert | false | - |
-| VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_VERSION | v1.104.0-cluster | false | - |
+| VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_VERSION | v1.105.0-cluster | false | - |
 | VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_PORT | 8480 | false | - |
 | VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_RESOURCE_LIMIT_MEM | 500Mi | false | - |
 | VM_VMCLUSTERDEFAULT_VMINSERTDEFAULT_RESOURCE_LIMIT_CPU | 500m | false | - |
@@ -100,7 +100,7 @@ aliases:
 | VM_VMALERTMANAGER_RESOURCE_REQUEST_CPU | 30m | false | - |
 | VM_DISABLESELFSERVICESCRAPECREATION | false | false | - |
 | VM_VMBACKUP_IMAGE | victoriametrics/vmbackupmanager | false | - |
-| VM_VMBACKUP_VERSION | v1.104.0-enterprise | false | - |
+| VM_VMBACKUP_VERSION | v1.105.0-enterprise | false | - |
 | VM_VMBACKUP_PORT | 8300 | false | - |
 | VM_VMBACKUP_USEDEFAULTRESOURCES | true | false | - |
 | VM_VMBACKUP_RESOURCE_LIMIT_MEM | 500Mi | false | - |
@@ -108,7 +108,7 @@ aliases:
 | VM_VMBACKUP_RESOURCE_REQUEST_MEM | 200Mi | false | - |
 | VM_VMBACKUP_RESOURCE_REQUEST_CPU | 150m | false | - |
 | VM_VMAUTHDEFAULT_IMAGE | victoriametrics/vmauth | false | - |
-| VM_VMAUTHDEFAULT_VERSION | v1.104.0 | false | - |
+| VM_VMAUTHDEFAULT_VERSION | v1.105.0 | false | - |
 | VM_VMAUTHDEFAULT_CONFIGRELOADIMAGE | quay.io/prometheus-operator/prometheus-config-reloader:v0.68.0 | false | - |
 | VM_VMAUTHDEFAULT_PORT | 8427 | false | - |
 | VM_VMAUTHDEFAULT_USEDEFAULTRESOURCES | true | false | - |
@@ -136,4 +136,4 @@ aliases:
 | VM_PODWAITREADYINTERVALCHECK | 5s | false | Defines poll interval for pods ready check at statefulset rollout update |
 | VM_FORCERESYNCINTERVAL | 60s | false | configures force resync interval for VMAgent, VMAlert, VMAlertmanager and VMAuth. |
 | VM_ENABLESTRICTSECURITY | false | false | EnableStrictSecurity will add default `securityContext` to pods and containers created by operator Default PodSecurityContext include: 1. RunAsNonRoot: true 2. RunAsUser/RunAsGroup/FSGroup: 65534 '65534' refers to 'nobody' in all the used default images like alpine, busybox. If you're using customize image, please make sure '65534' is a valid uid in there or specify SecurityContext. 3. FSGroupChangePolicy: &onRootMismatch If KubeVersion>=1.20, use `FSGroupChangePolicy="onRootMismatch"` to skip the recursive permission change when the root of the volume already has the correct permissions 4. SeccompProfile:      type: RuntimeDefault Use `RuntimeDefault` seccomp profile by default, which is defined by the container runtime, instead of using the Unconfined (seccomp disabled) mode. Default container SecurityContext include: 1. AllowPrivilegeEscalation: false 2. ReadOnlyRootFilesystem: true 3. Capabilities:      drop:        - all turn off `EnableStrictSecurity` by default, see https://github.com/VictoriaMetrics/operator/issues/749 for details |
-[envconfig-sum]: 41649232efe6d908b9a973655bf62dd3
\ No newline at end of file
+[envconfig-sum]: f319004a92b62b1dad0c3e51323365dc
\ No newline at end of file
diff --git a/docs/vmagent.md b/docs/vmagent.md
index 15334a0ae..45a693a3e 100644
--- a/docs/vmagent.md
+++ b/docs/vmagent.md
@@ -1662,7 +1662,7 @@ It is safe sharing the collected profiles from security point of view, since the
 
 `vmagent` can be fine-tuned with various command-line flags. Run `./vmagent -help` in order to see the full list of these flags with their descriptions and default values:
 
-```sh
+```shellhelp
 ./vmagent -help
 
 vmagent collects metrics data via popular data ingestion protocols and routes them to VictoriaMetrics.
diff --git a/docs/vmalert.md b/docs/vmalert.md
index 61a2e6ae3..107ff7f88 100644
--- a/docs/vmalert.md
+++ b/docs/vmalert.md
@@ -1029,7 +1029,7 @@ command-line flags with their descriptions.
 
 The shortlist of configuration flags is the following:
 
-```sh
+```shellhelp
   -clusterMode
      If clusterMode is enabled, then vmalert automatically adds the tenant specified in config groups to -datasource.url, -remoteWrite.url and -remoteRead.url. See https://docs.victoriametrics.com/vmalert/#multitenancy . This flag is available only in Enterprise binaries. See https://docs.victoriametrics.com/enterprise/
   -configCheckInterval duration
diff --git a/docs/vmauth.md b/docs/vmauth.md
index 5a798c229..f9e2c5614 100644
--- a/docs/vmauth.md
+++ b/docs/vmauth.md
@@ -1170,7 +1170,7 @@ It is safe sharing the collected profiles from security point of view, since the
 
 Pass `-help` command-line arg to `vmauth` in order to see all the configuration options:
 
-```sh
+```shellhelp
 ./vmauth -help
 
 vmauth authenticates and authorizes incoming requests and proxies them to VictoriaMetrics.
diff --git a/docs/vmbackup.md b/docs/vmbackup.md
index 365b02e7e..e58e200d3 100644
--- a/docs/vmbackup.md
+++ b/docs/vmbackup.md
@@ -325,7 +325,7 @@ Refer to the respective documentation for your object storage provider for more
 
 Run `vmbackup -help` in order to see all the available options:
 
-```sh
+```shellhelp
   -concurrency int
      The number of concurrent workers. Higher concurrency may reduce backup duration (default 10)
   -configFilePath string
diff --git a/docs/vmgateway.md b/docs/vmgateway.md
index ec9858085..88012b4d0 100644
--- a/docs/vmgateway.md
+++ b/docs/vmgateway.md
@@ -270,7 +270,7 @@ Example usage for tokens issued by Google:
 
 Below is the list of configuration flags (it can be viewed by running `./vmgateway -help`):
 
-```sh
+```shellhelp
   -auth.httpHeader string
      HTTP header name to look for JWT authorization token (default "Authorization")
   -auth.jwksEndpoints array
diff --git a/docs/vmrestore.md b/docs/vmrestore.md
index afb57d05a..f0ce35067 100644
--- a/docs/vmrestore.md
+++ b/docs/vmrestore.md
@@ -19,7 +19,7 @@ VictoriaMetrics must be stopped during the restore process.
 
 Run the following command to restore backup from the given `-src` into the given `-storageDataPath`:
 
-```sh
+```shellhelp
 ./vmrestore -src=<storageType>://<path/to/backup> -storageDataPath=<local/path/to/restore>
 ```
 


Test patch:
diff --git a/app/vmalert/web_types_test.go b/app/vmalert/web_types_test.go
index 40f5404a3..61574c170 100644
--- a/app/vmalert/web_types_test.go
+++ b/app/vmalert/web_types_test.go
@@ -1,9 +1,56 @@
 package main
 
 import (
+	"fmt"
+	"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/config"
+	"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/datasource"
+	"github.com/VictoriaMetrics/VictoriaMetrics/app/vmalert/rule"
+	"reflect"
 	"testing"
 )
 
+func TestRecordingToApi(t *testing.T) {
+	fq := &datasource.FakeQuerier{}
+	fq.Add(datasource.Metric{
+		Values: []float64{1}, Timestamps: []int64{0},
+	})
+	g := &rule.Group{
+		Name:        "group",
+		File:        "rules.yaml",
+		Concurrency: 1,
+	}
+
+	entriesLimit := 44
+	rr := rule.NewRecordingRule(fq, g, config.Rule{
+		ID:                 1248,
+		Record:             "record_name",
+		Expr:               "up",
+		Labels:             map[string]string{"label": "value"},
+		UpdateEntriesLimit: &entriesLimit,
+	})
+
+	expectedRes := apiRule{
+		Name:           "record_name",
+		Query:          "up",
+		Labels:         map[string]string{"label": "value"},
+		Health:         "ok",
+		Type:           ruleTypeRecording,
+		DatasourceType: "prometheus",
+		ID:             "1248",
+		GroupID:        fmt.Sprintf("%d", g.ID()),
+		GroupName:      "group",
+		File:           "rules.yaml",
+		MaxUpdates:     44,
+		Updates:        make([]rule.StateEntry, 0),
+	}
+
+	res := recordingToAPI(rr)
+
+	if !reflect.DeepEqual(res, expectedRes) {
+		t.Fatalf("expected to have: \n%v;\ngot: \n%v", expectedRes, res)
+	}
+}
+
 func TestUrlValuesToStrings(t *testing.T) {
 	mapQueryParams := map[string][]string{
 		"param1": {"param1"},