diff --git a/docs/guides/grafana-vmauth-openid-configuration/README.md b/docs/guides/grafana-vmauth-openid-configuration/README.md index 1579dfb7da..182f9707ac 100644 --- a/docs/guides/grafana-vmauth-openid-configuration/README.md +++ b/docs/guides/grafana-vmauth-openid-configuration/README.md @@ -240,23 +240,23 @@ vmagent will write data into VictoriaMetrics single-node and cluster (with tenan # compose.yaml services: vmsingle: - image: victoriametrics/victoria-metrics:v1.142.0 + image: victoriametrics/victoria-metrics:v1.143.0 vmstorage: - image: victoriametrics/vmstorage:v1.142.0-cluster + image: victoriametrics/vmstorage:v1.143.0-cluster vminsert: - image: victoriametrics/vminsert:v1.142.0-cluster + image: victoriametrics/vminsert:v1.143.0-cluster command: - -storageNode=vmstorage:8400 vmselect: - image: victoriametrics/vmselect:v1.142.0-cluster + image: victoriametrics/vmselect:v1.143.0-cluster command: - -storageNode=vmstorage:8401 vmagent: - image: victoriametrics/vmagent:v1.142.0 + image: victoriametrics/vmagent:v1.143.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml command: @@ -308,7 +308,7 @@ Now add the vmauth service to `compose.yaml`: # compose.yaml services: vmauth: - image: docker.io/victoriametrics/vmauth:v1.142.0 + image: docker.io/victoriametrics/vmauth:v1.143.0 ports: - 8427:8427 volumes: diff --git a/docs/guides/vmagent-openid-configuration/README.md b/docs/guides/vmagent-openid-configuration/README.md index 1ee375028e..6bd929c8a0 100644 --- a/docs/guides/vmagent-openid-configuration/README.md +++ b/docs/guides/vmagent-openid-configuration/README.md @@ -155,15 +155,15 @@ These services will store and query the metrics scraped by vmagent. # compose.yaml services: vmstorage: - image: victoriametrics/vmstorage:v1.142.0-cluster + image: victoriametrics/vmstorage:v1.143.0-cluster vminsert: - image: victoriametrics/vminsert:v1.142.0-cluster + image: victoriametrics/vminsert:v1.143.0-cluster command: - -storageNode=vmstorage:8400 vmselect: - image: victoriametrics/vmselect:v1.142.0-cluster + image: victoriametrics/vmselect:v1.143.0-cluster command: - -storageNode=vmstorage:8401 ports: @@ -196,7 +196,7 @@ Add the vmauth service to `compose.yaml`: # compose.yaml services: vmauth: - image: victoriametrics/vmauth:v1.142.0-enterprise + image: victoriametrics/vmauth:v1.143.0-enterprise ports: - 8427:8427 volumes: @@ -251,7 +251,7 @@ Add the vmagent service to `compose.yaml` with OAuth2 configuration: # compose.yaml services: vmagent: - image: victoriametrics/vmagent:v1.142.0 + image: victoriametrics/vmagent:v1.143.0 volumes: - ./scrape.yaml:/etc/vmagent/config.yaml command: diff --git a/docs/guides/vmalert-datasource-managed-alerts-grafana/README.md b/docs/guides/vmalert-datasource-managed-alerts-grafana/README.md index 392ff6ffe0..fa0bf9b9c0 100644 --- a/docs/guides/vmalert-datasource-managed-alerts-grafana/README.md +++ b/docs/guides/vmalert-datasource-managed-alerts-grafana/README.md @@ -107,7 +107,7 @@ The final piece is the Docker Compose file. This ties all the services together # compose.yml services: victoriametrics: - image: victoriametrics/victoria-metrics:v1.142.0 + image: victoriametrics/victoria-metrics:v1.143.0 command: - "--storageDataPath=/victoria-metrics-data" - "--selfScrapeInterval=10s" @@ -128,7 +128,7 @@ services: - ./alertmanager.yml:/etc/alertmanager/alertmanager.yml:ro vmalert: - image: victoriametrics/vmalert:v1.142.0 + image: victoriametrics/vmalert:v1.143.0 depends_on: - victoriametrics - alertmanager diff --git a/docs/victoriametrics/Quick-Start.md b/docs/victoriametrics/Quick-Start.md index 22e885d1f4..53f85e5617 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.142.0 +docker pull victoriametrics/victoria-metrics:v1.143.0 docker run -it --rm -v `pwd`/victoria-metrics-data:/victoria-metrics-data -p 8428:8428 \ - victoriametrics/victoria-metrics:v1.142.0 --selfScrapeInterval=5s -storageDataPath=victoria-metrics-data + victoriametrics/victoria-metrics:v1.143.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 b2991495d9..5679fd19ee 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.142.0-enterprise.tar.gz`. +Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.143.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.142.0/victoria-metrics-linux-amd64-v1.142.0-enterprise.tar.gz -tar -xzf victoria-metrics-linux-amd64-v1.142.0-enterprise.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.143.0/victoria-metrics-linux-amd64-v1.143.0-enterprise.tar.gz +tar -xzf victoria-metrics-linux-amd64-v1.143.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.142.0-enterprise`. +Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.143.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.142.0-enterprise -license=BASE64_ENCODED_LICENSE_KEY +docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.143.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.142.0-enterprise -licenseFile=/path/to/vm-license +docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.143.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.142.0 + image: victoriametrics/victoria-metrics:v1.143.0 ports: - 8428:8428 volumes: @@ -209,7 +209,7 @@ is used to provide the license key in plain-text: ```yaml server: image: - tag: v1.142.0-enterprise + tag: v1.143.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.142.0-enterprise + tag: v1.143.0-enterprise license: secret: @@ -270,7 +270,7 @@ spec: license: key: {BASE64_ENCODED_LICENSE_KEY} image: - tag: v1.142.0-enterprise + tag: v1.143.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.142.0-enterprise + tag: v1.143.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.142.0-enterprise.tar.gz` +`victoria-metrics-linux-amd64-v1.143.0-enterprise.tar.gz` Includes: @@ -347,7 +347,7 @@ Includes: Example Docker image: -`victoriametrics/victoria-metrics:v1.142.0-enterprise-fips` – uses the FIPS-compatible binary and based on `scratch` image. +`victoriametrics/victoria-metrics:v1.143.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 e6dbdfc497..02323ca1f6 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.142.0/victoria-metrics-linux-amd64-v1.142.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.142.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.143.0/victoria-metrics-linux-amd64-v1.143.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.143.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.142.0/victoria-metrics-linux-amd64-v1.142.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.142.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.143.0/victoria-metrics-linux-amd64-v1.143.0.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.143.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 72c6cc7529..8b8d77ddd7 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.142.0/vmutils-darwin-arm64-v1.142.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.143.0/vmutils-darwin-arm64-v1.143.0.tar.gz -tar xzf vmutils-darwin-arm64-v1.142.0.tar.gz +tar xzf vmutils-darwin-arm64-v1.143.0.tar.gz ``` Once binary is unpacked, see the full list of supported modes by running the following command: