VictoriaLogs

Released at 2026-10-02

v1.52.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaLogs enterprise. All these fixes are also included in the latest community release. The v1.52.x line will be supported for at least 12 months since v1.52.0 release

• SECURITY: upgrade Go builder from Go1.26.5 to Go1.26.8. See the list of issues addressed in Go1.26.6, Go1.26.7 and Go1.26.8.

• SECURITY: deletion API: restrict the /delete/run_task endpoint to the POST method only in order to prevent some SSRF-based log deletion attacks. See #1635.

• BUGFIX: Loki data ingestion: properly ignore structured metadata with empty values in protobuf requests. Previously, valid requests containing structured metadata with empty values were rejected. See #1757.

• BUGFIX: metrics: prevent vl_streams_created_total from decreasing when an old daily partition is removed. The metric now increases until restart, so Prometheus increase() no longer reports false spikes after old partitions are deleted. See #1461.

• BUGFIX: syslog data ingestion and unpack_syslog pipe: prevent a panic when an incomplete RFC5424 structured data parameter ends immediately after =. This could occur both when ingesting syslog messages and when parsing already stored messages with unpack_syslog. See #1786.

• BUGFIX: syslog data ingestion: rename the misspelled vl_udp_reqests_total metric to vl_udp_requests_total, so it matches the docs.

• BUGFIX: cluster version (vlinsert): now drains buffered logs to vlstorage nodes on graceful shutdown instead of dropping them, bounded by the new -insert.drainTimeout command-line flag (default 5s). See #1572.

• BUGFIX: cluster version: evenly spread rerouted data across available vlstorage nodes. Previously, healthy nodes adjacent to unavailable nodes in the -storageNode list could receive much more data, resulting in uneven resource usage. See #1548.

• BUGFIX: cluster version: properly cancel queries already running on vlstorage when the corresponding query is canceled or times out on vlselect. Previously, vlstorage could fail to detect the disconnected vlselect, causing these queries to continue running and waste CPU and disk IO. See [#1672](https://github.com/VictoriaMetrics/VictoriaLogs/issues

Released at 2026-08-18

• SECURITY: upgrade Go builder from Go1.26.4 to Go1.26.6. See the list of issues addressed in Go1.26.5 and the list of issues addressed in Go1.26.6.

• BUGFIX: cluster version: allow vlstorage v1.51.1 to accept requests from vlselect versions v1.38.0 through v1.51.0. This allows upgrading vlstorage nodes from older versions to v1.51.1 while vlselect nodes remain on the corresponding older version, and then upgrading the vlselect nodes to v1.51.1, without query downtime caused by an internal protocol mismatch. Starting from v1.52.0, vlstorage no longer accepts requests from vlselect v1.50.0 or earlier. See #1665.

Released at 2026-07-16

Update note 1: the base Docker image has been changed from Alpine to distroless in order to reduce an attack surface (The distroless base image doesn't contain any executables contrary to the Alpine base image). For debugging VictoriaLogs containers in Kubernetes it is recommended to use kubectl debug.

Update note 2: VictoriaLogs no longer provides a Docker image for the linux/386 platform because the distroless base image doesn't support this platform. Executable files for linux/386 platform are still published at the VictoriaLogs releases page.

Update note 3: VictoriaLogs cluster users upgrading from versions v1.38.0 through v1.50.0 should first upgrade all vlstorage nodes to v1.51.1, then upgrade all vlselect nodes to v1.51.1, and only then continue upgrading the cluster to v1.52.0. This avoids query downtime caused by incompatible internal protocol versions.

• SECURITY: upgrade Go builder from Go1.26.4 to Go1.26.5. See the list of issues addressed in Go1.26.5.

• FEATURE: switch base Docker image from Alpine to distroless for VictoriaLogs, vlagent and vlogscli. This reduces the image size and attack surface. See #1228.

• FEATURE: LogsQL: add json_array_concat pipe for joining JSON array items stored in the given log field into a string with the given delimiter. See #712.

• FEATURE: data ingestion: adjust _stream field value according to the actual log fields. This simplifies importing of previously modified VictoriaLogs-exported data. See #1122.

• FEATURE: vlagent: add -remoteWrite.basicAuth.usernameFile command-line flag for dynamically reloading basic auth username for the corresponding -remoteWrite.url from the given file. See operator#2371.

• FEATURE: web UI: improve hits chart tooltip timestamp display by hiding excessive precision. See #1533.

• FEATURE: web UI: add Quick start examples to autocomplete suggestions and show recent query history items alongside field and value suggestions. See #1498.

• FEATURE: web UI: persist query history in browser local storage and show the last run time for history items. See #1498.

• FEATURE: web UI: improve hits chart interval selector by using curated interval options and choosing a more suitable default step for the selected time

Released at 2026-06-17

Update Note 1: LogsQL: disallow using filter pipes without the filter prefix if the filter doesn't start with field_name: prefix. For example, foo | bar is disallowed now. It must be rewritten to one of the following equivalents: foo bar, foo | "bar", foo | _msg:bar or foo | filter bar. This reduces the chances of incorrectly written queries like in the #1454. However, this may be a breaking change if you have queries that filter without the filter prefix, such as ... | !foo, ... | {host="x"}, ... | >5 or ... | =foo - these now fail with unexpected pipe and must add the filter prefix (e.g. ... | filter !foo).

Update Note 2: cluster version: this release bumps the internal vlselect and vlstorage protocol version (see the queries-longer-than-10MB fix in #1462). A version mismatch between vlselect and vlstorage fails the request, so queries are expected to fail during a rolling upgrade while the cluster runs mixed versions. All the cluster components must be upgraded to this release or newer.

Update Note 3: VictoriaLogs cluster users upgrading from versions v1.38.0 through v1.50.0 should upgrade to v1.51.1 instead of this release. Upgrade all vlstorage nodes first, and then upgrade all vlselect nodes. This avoids query downtime caused by incompatible internal protocol versions.

• SECURITY: upgrade Go builder from Go1.26.2 to Go1.26.4. See the list of issues addressed in Go1.26.3 and the list of issues addressed in Go1.26.4.

• FEATURE: vmalert: add -vmalert.proxyURL command-line flag, which allows proxying /select/vmalert/* requests from VictoriaLogs to vmalert. See #90 and these docs.

• FEATURE: metrics: expose filesystem type for storage paths via the vm_fs_info metric. This helps identify filesystem-specific issues during troubleshooting. See #1435.

• FEATURE: LogsQL: allow putting ; in the end of the query. This is useful for detecting the end of multi-line query.

• FEATURE: LogsQL: add 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. Thanks to @warkadiusz for the pull request #904.

• FEATURE: querying API: allow using limit and offset pipes after the stats pipe in queries to [/select/logsql/stats_query