Welcome to the March release roundup of VictoriaMetrics Stack, covering key enhancements in VictoriaMetrics and VictoriaLogs. These updates deliver improved UI scalability, enhanced authentication flexibility, improved query performance, and logging tools that streamline observability workflows in production environments.

This roundup covers releases for:

• VictoriaMetrics
• VictoriaLogs

VictoriaMetrics v1.139.0, v1.138.0, and v1.137.0

#

VictoriaMetrics v1.139.0 release highlights

• Cardinality Explorer in Grafana: Added an experimental dashboard for exploring metric cardinality directly in Grafana.
• Improved VMUI scalability: Added pagination for alerts and rules in VMUI, making the UI easier to use with thousands of entries.
• vmauth improvements: JWT handling is now more flexible and standards-compliant, and basic auth no longer requires a username.
• Better OpenTelemetry compatibility: Added support for negative buckets in exponential histograms.
• Faster restores: vmrestore can now be significantly faster on Linux, with optimized write paths and file preallocation when the network is not the bottleneck.
• More robust cluster behavior: Improved handling of stale connections in vmselect, reducing query failures after vmstorage restarts.
• Improved NFS stability: Fixed a panic that could occur during directory deletion on NFS mounts.

As always, this release also includes bug fixes and smaller quality-of-life improvements.

New features in VictoriaMetrics v1.138.0

• vmauth access logs: Added an access_log option so per-user requests can be logged to stdout, with filtering by HTTP status codes for easier debugging of unusual traffic and request sources.
• JWT auth in vmauth: Expanded JWT tokens features. You can now use match_claims for JWT-based request routing, alongside support claim-based request templating, and OIDC Discovery for automatically fetching and rotating public keys.
• New and updated JWT guides: Expanded the JWT flow with guides for Grafana + VictoriaMetrics datasource setups, vmagent JWT token retrieval for remoteWrite, and vmgateway migration to vmauth.
• Bug fixes: Also shipped several fixes, including correct routing to default_url, improved histogram metadata handling, and vmauth dashboard memory panel fixes.

VictoriaMetrics v1.137.0 release highlights

• Cross-backend backups with vmbackup: Backups can now be copied between different storage backends, such as S3 to local disk or GCS to S3.
• JWT authentication in vmauth: Added JWT authentication with claim-based routing.
• macOS process metrics: All components now expose process-level metrics on macOS, including process_cpu_seconds_total and process_resident_memory_bytes.
• vmagent default debug UI restored: -promscrape.dropOriginalLabels now defaults to false, bringing back the Discovered targets UI without extra CPU or memory overhead.
• Metadata ingestion enabled by default: Metrics metadata ingestion and in-memory storage are now enabled by default, and can be disabled with -enableMetadata=false.
• New histogram_fraction function: Added a MetricsQL function for calculating bucket fractions between bounds, improving compatibility with SLO and SLI tooling.
• SBOM attestations for container images: Software Bill of Materials (SBOM) attestations are now published for Docker images in SPDX format, improving supply chain transparency and compliance.

VictoriaLogs v1.48.0 and v1.47.0

#

VictoriaLogs v1.48.0 release highlights

• Web UI sidebar: The built-in web UI now includes a sidebar for quick filtering by log stream fields and their values. This gives us a much faster way to narrow down noisy result sets without manually composing every filter from scratch. (Thanks to @hagen1778 and @Loori-R for pushing hard to implement this feature!)
• ignore_pipes support: Supporting that new sidebar, HTTP query endpoints can now ignore pipes when ignore_pipes=1 is passed as a query argument. In practice, this means helper requests for stream fields and values can still work even if the current query contains transformation pipes, so the UI can keep providing filtering options without being confused by the later stages of the query.
• CSV export: Query results from /select/logsql/query can now be returned as CSV by adding format=csv query argument. That makes it easier to export data into spreadsheets, reporting workflows, and external tools, and it also enables cleaner CSV downloads from the web UI.
• Kubernetes Namespace metadata: vlagent can now include Namespace labels and Namespace annotations in Kubernetes log entries. The same metadata is also available to -kubernetesCollector.excludeFilter even when you choose not to store it in every log entry, so unwanted logs can still be filtered out earlier in the pipeline.
• offset in total_stats: LogsQL now supports the offset modifier for first(...) and last(...) inside total_stats. This makes sequence analysis more practical because you are no longer limited to the earliest or latest event and can also inspect the second, third, or earlier items in the ordered set.
• last() in running_stats: running_stats now supports last(...), which can be used for comparing each record with the previously seen value. This is useful for spotting changes between consecutive events, such as state transitions, previous timestamps, or earlier field values.
• maxQueryLen limit: Users can now limit accepted query size with -search.maxQueryLen. This provides a straightforward guardrail against extremely long queries that would otherwise consume extra CPU and memory during parsing and execution.
• Ingestion stream skip: During ingestion, logs containing _stream or _stream_id are now skipped, and a warning is emitted for each affected entry. This prevents user-supplied fields from colliding with internally generated stream metadata, making ingestion behavior safer and easier to debug when input data is malformed.
• SBOM attestations for container images: Container images now publish Software Bill of Materials (SBOM) attestations for Docker images in SPDX format, improving supply chain transparency and compliance.

VictoriaLogs v1.47.0 release highlights

• json_array_contains_any filter: New json_array_contains_any(...) filter lets you filter logs by values inside JSON arrays such as tags=["prod","canary"], which makes it much easier to work with structured JSON logs without first reshaping the data.
• first/last in total_stats: total_stats now has first(...) and last(...), so you can pull the earliest and latest field values in a time range and analyze event sequences more directly.
• New stats pipe functions: The stats pipe gained any(...), field_max(...), and field_min(...), which makes it simpler to return a sample field value or the field attached to the highest or lowest point, without the extra unpacking work older patterns needed.
• Nested total_stats labels: stats_query and stats_query_range now allow total_stats by (...) to use a smaller set of labels than the preceding stats by (...), which helps when you want to roll up grouped results into cleaner totals for dashboards, alerting, or further analysis.
• Interval selector UI: The web UI replaces the old Bars control with an Interval selector on the hits chart, so choosing chart resolution is more intuitive and better aligned with the time range you are investigating.
• Improved hits chart: The hits chart is now easier to drill into. Clicking a bar sets the exact time range for that bucket, and zooming requires a minimum drag distance, reducing accidental selections during exploration.

Full Changelogs

#

Upgrade today to leverage these enhancements and explore the full changelogs for implementation details.

• VictoriaMetrics: v1.139.0, v1.138.0, and v1.137.0
• VictoriaLogs: v1.48.0, and v1.47.0

Stay tuned for more ecosystem updates from the VictoriaMetrics team. Thank you for reading!