VictoriaMetrics/victorialogs-datasource v0.27.0

on GitHub

FEATURE: add a visual query builder. Construct queries by chaining typed pipes (filter, aggregate, modify, sort, limit, custom) through an interactive UI with field name/value dropdowns and keyboard navigation. See Query builder docs and #578.

FEATURE: replace the /health endpoint in the datasource backend health check with a real query to /select/logsql/query. This verifies that the VictoriaLogs backend can actually serve log queries, not just that the HTTP server is up. See #599.

FEATURE: add OpenTelemetry preset to datasource configuration. When enabled, the preset auto-detects field format (snake_case / camelCase) of traceID and severity field from recent logs, then generates Derived Fields for trace_id and Log level rules for OTel severity — without manual configuration. See OpenTelemetry preset docs.

FEATURE: route "Filter for value" / "Filter out" actions in Grafana Explore into the extra_filters query parameter instead of mutating the main expr. The user's LogsQL stays untouched; added filters appear as removable chips under the query editor (via the existing Ad-hoc filters control). Dashboard behavior is unchanged — there Grafana keeps driving these clicks through ad-hoc template variables.

BUGFIX: protect Raw Logs queries from excessively large line limits. A hard upper bound of 10000 lines is now enforced on both the per-query Line limit and the datasource-wide Maximum lines settings; a confirmation dialog warns before committing a value above 1000 lines. See #613.

BUGFIX: fix interpolation of a query with the variable at the end of the line. See #614;

BUGFIX: skip the redundant /select/logsql/hits (logs volume) request for Range and Instant query types in Grafana Explore. The histogram is only meaningful for Raw Logs queries; for stats query types the main response already provides the chart. See #630.

BUGFIX: prevent the wildcard * value of a multi-value template variable from being wrapped in double quotes inside the in(...) operator during query interpolation. See pr #638.

BUGFIX: fix off-by-one ordering of query results where the first row appeared in the wrong position relative to the rest of the sorted output. See #625.