VictoriaMetrics/VictoriaLogs v1.50.0

on GitHub

v1.50.0

Released at 2026-04-14

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

• FEATURE: data ingestion: add an ability to send logs via Splunk data ingestion protocol. See these docs. See #710.

• FEATURE: vlagent: add an ability to collect logs from arbitrary files by specifying the glob pattern. See these docs and #1195.

• FEATURE: LogsQL: improve validation for stats switch(...) by rejecting empty switch() expressions and multiple default branches. This helps catch invalid queries earlier and avoids confusing results. See #1300.

• FEATURE: LogsLQ: add an ability to search across multiple log fields with the field_name_prefix*:filter syntax. See these docs for details. See #82.

• FEATURE: Loki data ingestion: Add an ability to add the given prefix to log field names parsed from JSON message. This may be used for avoiding clash between log stream labels and the automatically parsed log field names. See these docs for details. See #1127.

• FEATURE: Datadog: support default Datadog ingestion paths such as /api/v2/logs and /api/v1/validate in addition to the existing /insert/datadog/... paths. This eliminates the need to put vmauth in front of VictoriaLogs for adding /insert/datadog/ prefix to the paths requested by DataDog agent.

• BUGFIX: LogsQL: properly return the field value for the log with the maximum _time field from field_max(_time, field). Previously incorrect value could be returned. See #1294.

• BUGFIX: LogsQL: properly return the log entry with the maximum _time field from row_max(_time). Previously incorrect log could be returned.

• BUGFIX: LogsQL: consistently match logs on the interval [t-d ... t) when using _time:d filter at the timestamp t. This aligns with the semantics of start and end query args at querying API, which select logs on the [start ... end) time range. This also makes more consistent and expected the results returned from vmalert. See #1226 and #9753 at VictoriaMetrics.

• BUGFIX: LogsQL: return a parse error for invalid weekday names in the week_range filter. Previously they were silently treated as Sunday, which could lead to incorrect query results. See #1269.

• BUGFIX: Datadog data ingestion: properly ingest logs with tags without values, such as env:prod,foo, by storing foo with the no_label_value value. Previously this could crash VictoriaLogs during log ingestion. See #1303.

• BUGFIX: Kubernetes Collector: honor -defaultMsgValue for logs without message fields. Previously vlagent stored the hard-coded missing _msg field; ... text instead of the configured value when logs were collected via kubernetesCollector. See #1283.

• BUGFIX: /select/logsql/hits: fix invalid memory address or nil pointer dereference panic when the query passed to /select/logsql/hits contains union rows(...). The panic has been introduced in v1.49.0.

• BUGFIX: /select/logsql/hits: fix panic when the internal stats pipe generated for this endpoint uses hits both as a grouping field and as the result name. See #1278.

• BUGFIX: OpenTelemetry data ingestion: replace custom severity field with severity_number and severity_text to be compatible with other solutions. See #1246.

• BUGFIX: vlagent: hide sensitive values passed via -remoteWrite.headers in /metrics, /flags, and startup logs. Previously these values could be exposed in plain text.

• BUGFIX: storage: fix cannot read directory contents: open ... .DS_Store: not a directory panic when restarting VictoriaLogs on MacOS. See #996.

• BUGFIX: partitions lifecycle: fix querying logs after detaching, removing and then re-creating the same per-day partition before VictoriaLogs restart. Previously newly ingested logs could be missing from normal queries and from _stream:{...} filters until restart. See #657.

• BUGFIX: web UI: fix incorrect border colors. The issue was introduced in v1.49.0. See #1271.