diff --git a/deployment/docker/Makefile b/deployment/docker/Makefile index e9fb6413e5..68c8a4e955 100644 --- a/deployment/docker/Makefile +++ b/deployment/docker/Makefile @@ -3,8 +3,8 @@ DOCKER_REGISTRIES ?= docker.io quay.io DOCKER_NAMESPACE ?= victoriametrics -ROOT_IMAGE ?= alpine:3.23.3 -CERTS_IMAGE := alpine:3.23.3 +ROOT_IMAGE ?= alpine:3.23.4 +CERTS_IMAGE := alpine:3.23.4 GO_BUILDER_IMAGE := golang:1.26.3 diff --git a/deployment/docker/compose-vl-cluster.yml b/deployment/docker/compose-vl-cluster.yml index adfc117b81..6554d52f37 100644 --- a/deployment/docker/compose-vl-cluster.yml +++ b/deployment/docker/compose-vl-cluster.yml @@ -1,7 +1,7 @@ services: # Grafana instance configured with VictoriaLogs as datasource grafana: - image: grafana/grafana:12.3.1 + image: grafana/grafana:12.4.3 depends_on: - "victoriametrics" - "vmauth" @@ -20,7 +20,7 @@ services: # vector is logs collector. It collects logs according to vector.yml # and forwards them to VictoriaLogs vector: - image: docker.io/timberio/vector:0.46.X-distroless-libc + image: docker.io/timberio/vector:0.54.X-distroless-libc volumes: - type: bind source: /var/run/docker.sock @@ -73,7 +73,7 @@ services: # VictoriaMetrics instance, a single process responsible for # scraping, storing metrics and serve read requests. victoriametrics: - image: victoriametrics/victoria-metrics:v1.137.0 + image: victoriametrics/victoria-metrics:v1.143.0 volumes: - vmdata:/storage - ./prometheus-vl-cluster.yml:/etc/prometheus/prometheus.yml @@ -87,7 +87,7 @@ services: # It proxies query requests from vmalert to either VictoriaMetrics or VictoriaLogs, # depending on the requested path. vmauth: - image: victoriametrics/vmauth:v1.137.0 + image: victoriametrics/vmauth:v1.143.0 depends_on: - "victoriametrics" - "vlselect-1" @@ -103,7 +103,7 @@ services: # vmalert executes alerting and recording rules according to given rule type. vmalert: - image: victoriametrics/vmalert:v1.137.0 + image: victoriametrics/vmalert:v1.143.0 depends_on: - "vmauth" - "alertmanager" @@ -133,7 +133,7 @@ services: # alertmanager receives alerting notifications from vmalert # and distributes them according to --config.file. alertmanager: - image: prom/alertmanager:v0.30.1 + image: prom/alertmanager:v0.32.1 volumes: - ./alertmanager.yml:/config/alertmanager.yml command: diff --git a/deployment/docker/compose-vl-single.yml b/deployment/docker/compose-vl-single.yml index 91b8065725..5c075254c4 100644 --- a/deployment/docker/compose-vl-single.yml +++ b/deployment/docker/compose-vl-single.yml @@ -1,7 +1,7 @@ services: # Grafana instance configured with VictoriaLogs as datasource grafana: - image: grafana/grafana:12.3.1 + image: grafana/grafana:12.4.3 depends_on: - "victoriametrics" - "victorialogs" @@ -20,7 +20,7 @@ services: # vector is logs collector. It collects logs according to vector.yml # and forwards them to VictoriaLogs vector: - image: docker.io/timberio/vector:0.46.X-distroless-libc + image: docker.io/timberio/vector:0.54.X-distroless-libc volumes: - type: bind source: /var/run/docker.sock @@ -50,7 +50,7 @@ services: # VictoriaMetrics instance, a single process responsible for # scraping, storing metrics and serve read requests. victoriametrics: - image: victoriametrics/victoria-metrics:v1.137.0 + image: victoriametrics/victoria-metrics:v1.143.0 ports: - "8428:8428" volumes: @@ -66,7 +66,7 @@ services: # It proxies query requests from vmalert to either VictoriaMetrics or VictoriaLogs, # depending on the requested path. vmauth: - image: victoriametrics/vmauth:v1.137.0 + image: victoriametrics/vmauth:v1.143.0 depends_on: - "victoriametrics" - "victorialogs" @@ -80,7 +80,7 @@ services: # vmalert executes alerting and recording rules according to the given rule type. vmalert: - image: victoriametrics/vmalert:v1.137.0 + image: victoriametrics/vmalert:v1.143.0 depends_on: - "vmauth" - "alertmanager" @@ -110,7 +110,7 @@ services: # alertmanager receives alerting notifications from vmalert # and distributes them according to --config.file. alertmanager: - image: prom/alertmanager:v0.30.1 + image: prom/alertmanager:v0.32.1 volumes: - ./alertmanager.yml:/config/alertmanager.yml command: diff --git a/docs/victorialogs/CHANGELOG.md b/docs/victorialogs/CHANGELOG.md index 8597edc0bd..e536fb0beb 100644 --- a/docs/victorialogs/CHANGELOG.md +++ b/docs/victorialogs/CHANGELOG.md @@ -23,6 +23,7 @@ according to the following docs: ## tip * SECURITY: upgrade Go builder from Go1.26.2 to Go1.26.3. See [the list of issues addressed in Go1.26.3](https://github.com/golang/go/issues?q=milestone%3AGo1.26.3%20label%3ACherryPickApproved). +* SECURITY: upgrade base docker image (Alpine) from 3.23.3 to 3.23.4. See [Alpine 3.23.4 release notes](https://www.alpinelinux.org/posts/Alpine-3.20.10-3.21.7-3.22.4-3.23.4-released.html). * FEATURE: [LogsQL](https://docs.victoriametrics.com/victorialogs/logsql/): add [`coalesce` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#coalesce-pipe), which returns the first non-empty value from the given list of fields. This is useful when the same value may be stored under different field names across logs, such as `user_id`, `username` or `email`. The pipe can also return a default value when all the fields are empty. See [#690](https://github.com/VictoriaMetrics/VictoriaLogs/issues/690). Thanks to @warkadiusz for [the pull request #904](https://github.com/VictoriaMetrics/VictoriaLogs/pull/904). * FEATURE: [querying API](https://docs.victoriametrics.com/victorialogs/querying/): allow using [`limit`](https://docs.victoriametrics.com/victorialogs/logsql/#limit-pipe) and [`offset`](https://docs.victoriametrics.com/victorialogs/logsql/#offset-pipe) pipes after the [`stats` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#stats-pipe) in queries to [`/select/logsql/stats_query`](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-stats). This enables the usage for these pipes in [alerting and recording rules for VictoriaLogs](https://docs.victoriametrics.com/victorialogs/vmalert/). See [#1296](https://github.com/VictoriaMetrics/VictoriaLogs/issues/1296).