diff --git a/deployment/docker/docker-compose-cluster.yml b/deployment/docker/docker-compose-cluster.yml index 2aa6c8753..b18021b53 100644 --- a/deployment/docker/docker-compose-cluster.yml +++ b/deployment/docker/docker-compose-cluster.yml @@ -5,7 +5,7 @@ services: # And forward them to --remoteWrite.url vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.100.0 + image: victoriametrics/vmagent:v1.100.1 depends_on: - "vminsert" ports: @@ -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.100.0-cluster + image: victoriametrics/vmstorage:v1.100.1-cluster ports: - 8482 - 8400 @@ -51,7 +51,7 @@ services: restart: always vmstorage-2: container_name: vmstorage-2 - image: victoriametrics/vmstorage:v1.100.0-cluster + image: victoriametrics/vmstorage:v1.100.1-cluster ports: - 8482 - 8400 @@ -66,7 +66,7 @@ services: # pre-process them and distributes across configured vmstorage shards. vminsert: container_name: vminsert - image: victoriametrics/vminsert:v1.100.0-cluster + image: victoriametrics/vminsert:v1.100.1-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -81,7 +81,7 @@ services: # vmselect collects results from configured `--storageNode` shards. vmselect-1: container_name: vmselect-1 - image: victoriametrics/vmselect:v1.100.0-cluster + image: victoriametrics/vmselect:v1.100.1-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -94,7 +94,7 @@ services: restart: always vmselect-2: container_name: vmselect-2 - image: victoriametrics/vmselect:v1.100.0-cluster + image: victoriametrics/vmselect:v1.100.1-cluster depends_on: - "vmstorage-1" - "vmstorage-2" @@ -112,7 +112,7 @@ services: # It can be used as an authentication proxy. vmauth: container_name: vmauth - image: victoriametrics/vmauth:v1.100.0 + image: victoriametrics/vmauth:v1.100.1 depends_on: - "vmselect-1" - "vmselect-2" @@ -127,7 +127,7 @@ services: # vmalert executes alerting and recording rules vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.100.0 + image: victoriametrics/vmalert:v1.100.1 depends_on: - "vmauth" ports: diff --git a/deployment/docker/docker-compose-victorialogs.yml b/deployment/docker/docker-compose-victorialogs.yml index f0b903caa..8a38339e3 100644 --- a/deployment/docker/docker-compose-victorialogs.yml +++ b/deployment/docker/docker-compose-victorialogs.yml @@ -58,7 +58,7 @@ services: # scraping, storing metrics and serve read requests. victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - 8428:8428 volumes: diff --git a/deployment/docker/docker-compose.yml b/deployment/docker/docker-compose.yml index d888260de..5b5a32592 100644 --- a/deployment/docker/docker-compose.yml +++ b/deployment/docker/docker-compose.yml @@ -5,7 +5,7 @@ services: # And forward them to --remoteWrite.url vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.100.0 + image: victoriametrics/vmagent:v1.100.1 depends_on: - "victoriametrics" ports: @@ -23,7 +23,7 @@ services: # storing metrics and serve read requests. victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - 8428:8428 - 8089:8089 @@ -66,7 +66,7 @@ services: # vmalert executes alerting and recording rules vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.100.0 + image: victoriametrics/vmalert:v1.100.1 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 1696618c6..71bd37212 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.100.0 + image: victoriametrics/vmagent:v1.100.1 depends_on: - "victoriametrics" ports: @@ -18,7 +18,7 @@ services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - 8428:8428 volumes: @@ -51,7 +51,7 @@ services: vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.100.0 + image: victoriametrics/vmalert:v1.100.1 depends_on: - "victoriametrics" ports: diff --git a/deployment/logs-benchmark/docker-compose.yml b/deployment/logs-benchmark/docker-compose.yml index 25dce8655..b93ca83fa 100644 --- a/deployment/logs-benchmark/docker-compose.yml +++ b/deployment/logs-benchmark/docker-compose.yml @@ -46,7 +46,7 @@ services: - '--config=/config.yml' vmsingle: - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - '8428:8428' command: diff --git a/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click b/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click index 4d967a302..bac89dfd4 100755 --- a/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click +++ b/deployment/marketplace/digitialocean/one-click-droplet/files/etc/update-motd.d/99-one-click @@ -19,8 +19,8 @@ On the server: * VictoriaMetrics is running on ports: 8428, 8089, 4242, 2003 and they are bound to the local interface. ******************************************************************************** - # This image includes v1.100.0 release of VictoriaMetrics. - # See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.100.0 + # This image includes v1.100.1 release of VictoriaMetrics. + # See Release notes https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.100.1 # Welcome to VictoriaMetrics droplet! diff --git a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md index 529d893c0..098d51ec3 100644 --- a/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md +++ b/docs/anomaly-detection/guides/guide-vmanomaly-vmalert.md @@ -19,9 +19,9 @@ aliases: - 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/Single-server-VictoriaMetrics.html) (v1.100.0) - - [vmalert](https://docs.victoriametrics.com/vmalert.html) (v1.100.0) - - [vmagent](https://docs.victoriametrics.com/vmagent.html) (v1.100.0) + - [VictoriaMetrics Single-Node](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html) (v1.100.1) + - [vmalert](https://docs.victoriametrics.com/vmalert.html) (v1.100.1) + - [vmagent](https://docs.victoriametrics.com/vmagent.html) (v1.100.1) - [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) @@ -328,7 +328,7 @@ Let's wrap it all up together into the `docker-compose.yml` file. services: vmagent: container_name: vmagent - image: victoriametrics/vmagent:v1.100.0 + image: victoriametrics/vmagent:v1.100.1 depends_on: - "victoriametrics" ports: @@ -345,7 +345,7 @@ services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - 8428:8428 volumes: @@ -378,7 +378,7 @@ services: vmalert: container_name: vmalert - image: victoriametrics/vmalert:v1.100.0 + image: victoriametrics/vmalert:v1.100.1 depends_on: - "victoriametrics" ports: diff --git a/docs/enterprise.md b/docs/enterprise.md index 33b3ab68a..2ec3a41b7 100644 --- a/docs/enterprise.md +++ b/docs/enterprise.md @@ -84,7 +84,7 @@ VictoriaMetrics Enterprise components are available in the following forms: It is allowed to run VictoriaMetrics Enterprise components in [cases listed here](#valid-cases-for-victoriametrics-enterprise). Binary releases of VictoriaMetrics Enterprise are available [at the releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest). -Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.100.0-enterprise.tar.gz`. +Enterprise binaries and packages have `enterprise` suffix in their names. For example, `victoria-metrics-linux-amd64-v1.100.1-enterprise.tar.gz`. In order to run binary release of VictoriaMetrics Enterprise component, please download the `*-enterprise.tar.gz` archive for your OS and architecture from the [releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest) and unpack it. Then run the unpacked binary. @@ -101,8 +101,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.100.0/victoria-metrics-linux-amd64-v1.100.0-enterprise.tar.gz -tar -xzf victoria-metrics-linux-amd64-v1.100.0-enterprise.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.100.1/victoria-metrics-linux-amd64-v1.100.1-enterprise.tar.gz +tar -xzf victoria-metrics-linux-amd64-v1.100.1-enterprise.tar.gz ./victoria-metrics-prod -license=BASE64_ENCODED_LICENSE_KEY ``` @@ -117,7 +117,7 @@ Alternatively, VictoriaMetrics Enterprise license can be stored in the file and It is allowed to run VictoriaMetrics Enterprise components in [cases listed here](#valid-cases-for-victoriametrics-enterprise). Docker images for VictoriaMetrics Enterprise are available [at VictoriaMetrics DockerHub](https://hub.docker.com/u/victoriametrics). -Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.100.0-enteprise`. +Enterprise docker images have `enterprise` suffix in their names. For example, `victoriametrics/victoria-metrics:v1.100.1-enterprise`. In order to run Docker image of VictoriaMetrics Enterprise component, it is required to provide the license key via command-line flag as described [here](#binary-releases). @@ -127,13 +127,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.100.0-enteprise -license=BASE64_ENCODED_LICENSE_KEY +docker run --name=victoria-metrics victoriametrics/victoria-metrics:v1.100.1-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.100.0-enteprise -licenseFile=/path/to/vm-license +docker run --name=victoria-metrics -v /vm-license:/vm-license victoriametrics/victoria-metrics:v1.100.1-enterprise -licenseFile=/path/to/vm-license ``` Example docker-compose configuration: @@ -142,7 +142,7 @@ version: "3.5" services: victoriametrics: container_name: victoriametrics - image: victoriametrics/victoria-metrics:v1.100.0 + image: victoriametrics/victoria-metrics:v1.100.1 ports: - 8428:8428 volumes: @@ -174,7 +174,7 @@ is used to provide key in plain-text: ```yaml server: image: - tag: v1.100.0-enterprise + tag: v1.100.1-enterprise license: key: {BASE64_ENCODED_LICENSE_KEY} @@ -185,7 +185,7 @@ In order to provide key via existing secret, the following values file is used: ```yaml server: image: - tag: v1.100.0-enterprise + tag: v1.100.1-enterprise license: secret: @@ -232,7 +232,7 @@ spec: license: key: {BASE64_ENCODED_LICENSE_KEY} image: - tag: v1.100.0-enterprise + tag: v1.100.1-enterprise ``` In order to provide key via existing secret, the following custom resource is used: @@ -249,7 +249,7 @@ spec: name: vm-license key: license image: - tag: v1.100.0-enterprise + tag: v1.100.1-enterprise ``` Example secret with license key: diff --git a/docs/scrape_config_examples.md b/docs/scrape_config_examples.md index 113390554..788d197ae 100644 --- a/docs/scrape_config_examples.md +++ b/docs/scrape_config_examples.md @@ -34,8 +34,8 @@ scrape_configs: After you created the `scrape.yaml` file, download and unpack [single-node VictoriaMetrics](https://docs.victoriametrics.com/) to the same directory: ``` -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.100.0/victoria-metrics-linux-amd64-v1.100.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.100.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.100.1/victoria-metrics-linux-amd64-v1.100.1.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.100.1.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/) acco ```yaml # Download and unpack single-node VictoriaMetrics -wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.100.0/victoria-metrics-linux-amd64-v1.100.0.tar.gz -tar xzf victoria-metrics-linux-amd64-v1.100.0.tar.gz +wget https://github.com/VictoriaMetrics/VictoriaMetrics/releases/download/v1.100.1/victoria-metrics-linux-amd64-v1.100.1.tar.gz +tar xzf victoria-metrics-linux-amd64-v1.100.1.tar.gz # Run single-node VictoriaMetrics with the given scrape.yaml ./victoria-metrics-prod -promscrape.config=scrape.yaml