From bc8f6c56882cacca43f6d99cbe9afa6459081ada Mon Sep 17 00:00:00 2001 From: f41gh7 Date: Mon, 19 Jan 2026 14:28:00 +0100 Subject: [PATCH] docs: point examples to the v1.134.0 release --- deployment/docker/compose-vm-cluster.yml | 18 ++++++------- deployment/docker/compose-vm-single.yml | 6 ++--- .../vmanomaly-integration/compose.yml | 6 ++--- .../guides/guide-vmanomaly-vmalert/README.md | 12 ++++----- .../README.md | 16 ++++++------ docs/victoriametrics/Quick-Start.md | 4 +-- docs/victoriametrics/enterprise.md | 26 +++++++++---------- .../victoriametrics/scrape_config_examples.md | 8 +++--- docs/victoriametrics/vmctl/vmctl.md | 4 +-- 9 files changed, 50 insertions(+), 50 deletions(-) diff --git a/deployment/docker/compose-vm-cluster.yml b/deployment/docker/compose-vm-cluster.yml index 7f67bf8f6a..dba2741434 100644 --- a/deployment/docker/compose-vm-cluster.yml +++ b/deployment/docker/compose-vm-cluster.yml @@ -3,7 +3,7 @@ services: # It scrapes targets defined in --promscrape.config # And forward them to --remoteWrite.url vmagent: - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 depends_on: - "vmauth" ports: @@ -37,14 +37,14 @@ services: # vmstorage shards. Each shard receives 1/N of all metrics sent to vminserts, # where N is number of vmstorages (2 in this case). vmstorage-1: - image: victoriametrics/vmstorage:v1.133.0-cluster + image: victoriametrics/vmstorage:v1.134.0-cluster volumes: - strgdata-1:/storage command: - "--storageDataPath=/storage" restart: always vmstorage-2: - image: victoriametrics/vmstorage:v1.133.0-cluster + image: victoriametrics/vmstorage:v1.134.0-cluster volumes: - strgdata-2:/storage command: @@ -54,7 +54,7 @@ services: # vminsert is ingestion frontend. It receives metrics pushed by vmagent, # pre-process them and distributes across configured vmstorage shards. vminsert-1: - image: victoriametrics/vminsert:v1.133.0-cluster + image: victoriametrics/vminsert:v1.134.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -63,7 +63,7 @@ services: - "--storageNode=vmstorage-2:8400" restart: always vminsert-2: - image: victoriametrics/vminsert:v1.133.0-cluster + image: victoriametrics/vminsert:v1.134.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -75,7 +75,7 @@ services: # vmselect is a query fronted. It serves read queries in MetricsQL or PromQL. # vmselect collects results from configured `--storageNode` shards. vmselect-1: - image: victoriametrics/vmselect:v1.133.0-cluster + image: victoriametrics/vmselect:v1.134.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -85,7 +85,7 @@ services: - "--vmalert.proxyURL=http://vmalert:8880" restart: always vmselect-2: - image: victoriametrics/vmselect:v1.133.0-cluster + image: victoriametrics/vmselect:v1.134.0-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -100,7 +100,7 @@ services: # read requests from Grafana, vmui, vmalert among vmselects. # It can be used as an authentication proxy. vmauth: - image: victoriametrics/vmauth:v1.133.0 + image: victoriametrics/vmauth:v1.134.0 depends_on: - "vmselect-1" - "vmselect-2" @@ -114,7 +114,7 @@ services: # vmalert executes alerting and recording rules vmalert: - image: victoriametrics/vmalert:v1.133.0 + image: victoriametrics/vmalert:v1.134.0 depends_on: - "vmauth" ports: diff --git a/deployment/docker/compose-vm-single.yml b/deployment/docker/compose-vm-single.yml index 920f99e017..b0d43fb1cc 100644 --- a/deployment/docker/compose-vm-single.yml +++ b/deployment/docker/compose-vm-single.yml @@ -3,7 +3,7 @@ services: # It scrapes targets defined in --promscrape.config # And forward them to --remoteWrite.url vmagent: - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 depends_on: - "victoriametrics" ports: @@ -18,7 +18,7 @@ services: # VictoriaMetrics instance, a single process responsible for # storing metrics and serve read requests. victoriametrics: - image: victoriametrics/victoria-metrics:v1.133.0 + image: victoriametrics/victoria-metrics:v1.134.0 ports: - 8428:8428 - 8089:8089 @@ -54,7 +54,7 @@ services: # vmalert executes alerting and recording rules vmalert: - image: victoriametrics/vmalert:v1.133.0 + image: victoriametrics/vmalert:v1.134.0 depends_on: - "victoriametrics" - "alertmanager" diff --git a/deployment/docker/vmanomaly/vmanomaly-integration/compose.yml b/deployment/docker/vmanomaly/vmanomaly-integration/compose.yml index bb4290c92f..690b4572fb 100644 --- a/deployment/docker/vmanomaly/vmanomaly-integration/compose.yml +++ b/deployment/docker/vmanomaly/vmanomaly-integration/compose.yml @@ -1,6 +1,6 @@ services: vmagent: - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 depends_on: - "victoriametrics" ports: @@ -14,7 +14,7 @@ services: restart: always victoriametrics: - image: victoriametrics/victoria-metrics:v1.133.0 + image: victoriametrics/victoria-metrics:v1.134.0 ports: - 8428:8428 volumes: @@ -40,7 +40,7 @@ services: restart: always vmalert: - image: victoriametrics/vmalert:v1.133.0 + image: victoriametrics/vmalert:v1.134.0 depends_on: - "victoriametrics" ports: diff --git a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md index b95bce8287..eb0fb9671c 100644 --- a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md +++ b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert/README.md @@ -10,9 +10,9 @@ sitemap: - To use *vmanomaly*, part of the enterprise package, a license key is required. Obtain your key [here](https://victoriametrics.com/products/enterprise/trial/) for this tutorial or for enterprise use. - In the tutorial, we'll be using the following VictoriaMetrics components: - - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) (v1.133.0) - - [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/) (v1.133.0) - - [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) (v1.133.0) + - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) (v1.134.0) + - [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/) (v1.134.0) + - [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) (v1.134.0) - [Grafana](https://grafana.com/) (v.10.2.1) - [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/) - [Node exporter](https://github.com/prometheus/node_exporter#node-exporter) (v1.7.0) and [Alertmanager](https://prometheus.io/docs/alerting/latest/alertmanager/) (v0.27.0) @@ -323,7 +323,7 @@ Let's wrap it all up together into the `docker-compose.yml` file. services: vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 depends_on: - "victoriametrics" ports: @@ -340,7 +340,7 @@ services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.133.0 + image: victoriametrics/victoria-metrics:v1.134.0 ports: - 8428:8428 volumes: @@ -373,7 +373,7 @@ services: vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.133.0 + image: victoriametrics/vmalert:v1.134.0 depends_on: - "victoriametrics" ports: diff --git a/docs/guides/grafana-vmgateway-openid-configuration/README.md b/docs/guides/grafana-vmgateway-openid-configuration/README.md index 67b12eceb9..43a52fb400 100644 --- a/docs/guides/grafana-vmgateway-openid-configuration/README.md +++ b/docs/guides/grafana-vmgateway-openid-configuration/README.md @@ -249,27 +249,27 @@ services: - grafana_data:/var/lib/grafana/ vmsingle: - image: victoriametrics/victoria-metrics:v1.133.0 + image: victoriametrics/victoria-metrics:v1.134.0 command: - -httpListenAddr=0.0.0.0:8429 vmstorage: - image: victoriametrics/vmstorage:v1.133.0-cluster + image: victoriametrics/vmstorage:v1.134.0-cluster vminsert: - image: victoriametrics/vminsert:v1.133.0-cluster + image: victoriametrics/vminsert:v1.134.0-cluster command: - -storageNode=vmstorage:8400 - -httpListenAddr=0.0.0.0:8480 vmselect: - image: victoriametrics/vmselect:v1.133.0-cluster + image: victoriametrics/vmselect:v1.134.0-cluster command: - -storageNode=vmstorage:8401 - -httpListenAddr=0.0.0.0:8481 vmagent: - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml command: @@ -278,7 +278,7 @@ services: - -remoteWrite.url=http://vmsingle:8429/api/v1/write vmgateway-cluster: - image: victoriametrics/vmgateway:v1.133.0-enterprise + image: victoriametrics/vmgateway:v1.134.0-enterprise ports: - 8431:8431 volumes: @@ -294,7 +294,7 @@ services: - -auth.oidcDiscoveryEndpoints=http://keycloak:8080/realms/master/.well-known/openid-configuration vmgateway-single: - image: victoriametrics/vmgateway:v1.133.0-enterprise + image: victoriametrics/vmgateway:v1.134.0-enterprise ports: - 8432:8431 volumes: @@ -405,7 +405,7 @@ Once iDP configuration is done, vmagent configuration needs to be updated to use ```yaml vmagent: - image: victoriametrics/vmagent:v1.133.0 + image: victoriametrics/vmagent:v1.134.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml - ./vmagent-client-secret:/etc/vmagent/oauth2-client-secret diff --git a/docs/victoriametrics/Quick-Start.md b/docs/victoriametrics/Quick-Start.md index 2ca939cb43..22af7101fa 100644 --- a/docs/victoriametrics/Quick-Start.md +++ b/docs/victoriametrics/Quick-Start.md @@ -58,9 +58,9 @@ Download the newest available [VictoriaMetrics release](https://docs.victoriamet from [DockerHub](https://hub.docker.com/r/victoriametrics/victoria-metrics) or [Quay](https://quay.io/repository/victoriametrics/victoria-metrics?tab=tags): ```sh -docker pull victoriametrics/victoria-metrics:v1.133.0 +docker pull victoriametrics/victoria-metrics:v1.134.0 docker run -it --rm -v `pwd`/victoria-metrics-data:/victoria-metrics-data -p 8428:8428 \ - victoriametrics/victoria-metrics:v1.133.0 --selfScrapeInterval=5s -storageDataPath=victoria-metrics-data + victoriametrics/victoria-metrics:v1.134.0 --selfScrapeInterval=5s -storageDataPath=victoria-metrics-data ``` _For Enterprise images see [this link](https://docs.victoriametrics.com/victoriametrics/enterprise/#docker-images)._ diff --git a/docs/victoriametrics/enterprise.md b/docs/victoriametrics/enterprise.md index 79b7b8199f..6c483d2b6f 100644 --- a/docs/victoriametrics/enterprise.md +++ b/docs/victoriametrics/enterprise.md @@ -117,7 +117,7 @@ It is allowed to run VictoriaMetrics and VictoriaLogs Enterprise components in [ Binary releases of Enterprise components are available at [the releases page for VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest) and [the releases page for VictoriaLogs](https://github.com/VictoriaMetrics/VictoriaLogs/releases/latest). -Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.133.0-enterprise.tar.gz`. +Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.134.0-enterprise.tar.gz`. In order to run binary release of Enterprise component, please download the `*-enterprise.tar.gz` archive for your OS and architecture from the corresponding releases page and unpack it. Then run the unpacked binary. @@ -135,8 +135,8 @@ For example, the following command runs VictoriaMetrics Enterprise binary with t obtained at [this page](https://victoriametrics.com/products/enterprise/trial/): ```sh -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.133.0/victoria-metrics-linux-amd64-v1.133.0-enterprise.tar.gz -tar -xzf victoria-metrics-linux-amd64-v1.133.0-enterprise.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.134.0/victoria-metrics-linux-amd64-v1.134.0-enterprise.tar.gz +tar -xzf victoria-metrics-linux-amd64-v1.134.0-enterprise.tar.gz ./victoria-metrics-prod -license=BASE64_ENCODED_LICENSE_KEY ``` @@ -151,7 +151,7 @@ Alternatively, VictoriaMetrics Enterprise license can be stored in the file and It is allowed to run VictoriaMetrics and VictoriaLogs Enterprise components in [cases listed here](#valid-cases-for-victoriametrics-enterprise). Docker images for Enterprise components are available at [VictoriaMetrics Docker Hub](https://hub.docker.com/u/victoriametrics) and [VictoriaMetrics Quay](https://quay.io/organization/victoriametrics). -Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.133.0-enterprise`. +Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.134.0-enterprise`. In order to run Docker image of VictoriaMetrics Enterprise component, it is required to provide the license key via the command-line flag as described in the [binary-releases](#binary-releases) section. @@ -161,13 +161,13 @@ Enterprise license key can be obtained at [this page](https://victoriametrics.co For example, the following command runs VictoriaMetrics Enterprise Docker image with the specified license key: ```sh -docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.133.0-enterprise -license=BASE64_ENCODED_LICENSE_KEY +docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.134.0-enterprise -license=BASE64_ENCODED_LICENSE_KEY ``` Alternatively, the license code can be stored in the file and then referred via `-licenseFile` command-line flag: ```sh -docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.133.0-enterprise -licenseFile=/path/to/vm-license +docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.134.0-enterprise -licenseFile=/path/to/vm-license ``` Example docker-compose configuration: @@ -177,7 +177,7 @@ version: "3.5" services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.133.0 + image: victoriametrics/victoria-metrics:v1.134.0 ports: - 8428:8428 volumes: @@ -209,7 +209,7 @@ is used to provide the license key in plain-text: ```yaml server: image: - tag: v1.133.0-enterprise + tag: v1.134.0-enterprise license: key: {BASE64_ENCODED_LICENSE_KEY} @@ -220,7 +220,7 @@ In order to provide the license key via existing secret, the following values fi ```yaml server: image: - tag: v1.133.0-enterprise + tag: v1.134.0-enterprise license: secret: @@ -270,7 +270,7 @@ spec: license: key: {BASE64_ENCODED_LICENSE_KEY} image: - tag: v1.133.0-enterprise + tag: v1.134.0-enterprise ``` In order to provide the license key via an existing secret, the following custom resource is used: @@ -287,7 +287,7 @@ spec: name: vm-license key: license image: - tag: v1.133.0-enterprise + tag: v1.134.0-enterprise ``` Example secret with license key: @@ -338,7 +338,7 @@ Builds are available for amd64 and arm64 architectures. Example archive: -`victoria-metrics-linux-amd64-v1.133.0-enterprise.tar.gz` +`victoria-metrics-linux-amd64-v1.134.0-enterprise.tar.gz` Includes: @@ -347,7 +347,7 @@ Includes: Example Docker image: -`victoriametrics/victoria-metrics:v1.133.0-enterprise-fips` – uses the FIPS-compatible binary and based on `scratch` image. +`victoriametrics/victoria-metrics:v1.134.0-enterprise-fips` – uses the FIPS-compatible binary and based on `scratch` image. ## Monitoring license expiration diff --git a/docs/victoriametrics/scrape_config_examples.md b/docs/victoriametrics/scrape_config_examples.md index bd6f54abb8..71e7281ba9 100644 --- a/docs/victoriametrics/scrape_config_examples.md +++ b/docs/victoriametrics/scrape_config_examples.md @@ -35,8 +35,8 @@ scrape_configs: After you created the `scrape.yaml` file, download and unpack [single-node VictoriaMetrics](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) to the same directory: ```sh -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.133.0/victoria-metrics-linux-amd64-v1.133.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.133.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.134.0/victoria-metrics-linux-amd64-v1.134.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.134.0.tar.gz ``` Then start VictoriaMetrics and instruct it to scrape targets defined in `scrape.yaml` and save scraped metrics @@ -150,8 +150,8 @@ Then start [single-node VictoriaMetrics](https://docs.victoriametrics.com/victor ```yaml # Download and unpack single-node VictoriaMetrics -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.133.0/victoria-metrics-linux-amd64-v1.133.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.133.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.134.0/victoria-metrics-linux-amd64-v1.134.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.134.0.tar.gz # Run single-node VictoriaMetrics with the given scrape.yaml ./victoria-metrics-prod -promscrape.config=scrape.yaml diff --git a/docs/victoriametrics/vmctl/vmctl.md b/docs/victoriametrics/vmctl/vmctl.md index e398b46671..a7c57d1470 100644 --- a/docs/victoriametrics/vmctl/vmctl.md +++ b/docs/victoriametrics/vmctl/vmctl.md @@ -34,9 +34,9 @@ vmctl command-line tool is available as: Download and unpack vmctl: ```sh -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.133.0/vmutils-darwin-arm64-v1.133.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.134.0/vmutils-darwin-arm64-v1.134.0.tar.gz -tar xzf vmutils-darwin-arm64-v1.133.0.tar.gz +tar xzf vmutils-darwin-arm64-v1.134.0.tar.gz ``` Once binary is unpacked, see the full list of supported modes by running the following command: