Released at 2025-08-27
-
FEATURE: HTTP querying APIs: return the actual query execution time in the
VL-Request-Duration-Seconds
HTTP response header. This will be used for displaying the query execution time at vlogscli, at the built-in web UI and at Grafana plugin for VictoriaLogs. -
FEATURE:
/select/logsql/stats_query_range
and/select/logsql/hits
: returnVL-Selected-Time-Range
HTTP response header, which contains the original time range specified in the query without taking into accountstart
andend
query args. The time range is returned as[start, end]
, wherestart
andend
are unix timestamps in nanoseconds. This header is needed for built-in web UI in order to adjust the displayed time range to the time range specified by the user in the query. See #558. -
FEATURE:
/select/logsql/hits
: take into account pipes, which do not modify the_time
field, when calculating hits for the given query on the given time range. Previously all the pipes in the query were ignored. This could lead to unexpected results. For example,* | extract "statusCode=<statusCode>," | filter statusCode:200
query was returning hits for all the logs instead of returning hits only for the logs containing the givenstatusCode
. See this comment. -
FEATURE: querying HTTP APIs: take into account all the pipes specified in the query when returning the requested field names, field values and logs steams from
/select/logsql/field_names
,/select/logsql/field_values
,/select/logsql/stream_field_names
,/select/logsql/stream_field_values
,/select/logsql/streams
and/select/logsql/stream_ids
HTTP endpoints. This makes more expected the auto-completetion results at the built-in web UI and at the Grafana plugin for VictoriaLogs. See this comment. -
FEATURE: web UI: show query execution time. See #602 for details.
-
BUGFIX: LogsQL: properly match newlines with '.' char in regular expressions used by
extract_regexp
andreplace_regexp
pipes. See #88. -
BUGFIX: querying HTTP APIs: properly parse
end
query arg if it contains a numeric timestamp, which can be represented as RFC3339 timestamp with zero nanoseconds (e.g. only microseconds, milliseconds or seconds are non-zero). See #587. -
BUGFIX: vlselect: return
502 Bad Gateway
http response code when one of thevlstorage
servers are unavailable. Previously400 Bad Request
http response code was incorrectly returned in this case. This helps building proper failover scheme in high-availability setups for VictoriaLogs. See #576. -
BUGFIX: web UI: fix incorrect logs sorting on the Group tab. See #579 for details.
-
BUGFIX: web UI: add button to control offset of live tailing. See #577 for details.
-
BUGFIX: web UI: escape value with double quotes when converting to a field filter.