The Vector team is excited to announce version 0.54.0!
vector top with new keybinds for scrolling, sorting, and filtering. Press ? to
see all available keybinds.datadog_logs sink now defaults to zstd compression instead of no compression, resulting
in better network efficiency and higher throughput.component_latency_seconds histogram and component_latency_mean_seconds gauge internal
metrics, exposing the time an event spends in a component.azure_logs_ingestion sink that supports the Azure Monitor Logs Ingestion API.
The existing azure_monitor_logs sink is now deprecated, and users should migrate before
Microsoft ends support for the old Data Collector API (currently scheduled for September 2026).datadog_logs sink now defaults to zstd compression. You can explicitly set compression to preserve
previous behavior.Add support for the Azure Monitor Logs Ingestion API through a new azure_logs_ingestion sink.
The azure_monitor_logs sink is now deprecated, and current users will need to migrate to azure_logs_ingestion before Microsoft end support for the old Data Collector API (currently scheduled for September 2026).
vector top for scrolling, sorting and filtering. You can now press ? when using vector top to see all available keybinds.host_metrics source filesystem collector on unix systems. The filesystem_inodes_total, filesystem_inodes_free, filesystem_inodes_used, and filesystem_inodes_used_ratio metrics are now available.azure_blob sink now supports routing requests through HTTP/HTTPS proxies, enabling uploads from restricted networks that require an outbound proxy.clickhouse sink now supports complex data types (Array, Map, and Tuple) when using the arrow_stream format.prometheus_remote_write sink now supports the healthcheck.uri field to customize the healthcheck endpoint.Upgrades the syslog encoding transform with three major improvements:
Structured Data Enhancements (RFC 5424):
tags="["tag1","tag2","tag3"]" (RFC 5424 spec doesn’t define how to handle arrays in structured data)UTF-8 Safety Fix:
RFC 3164 Compliance Improvements:
arrow_stream codec now uses arrow-json instead of serde_arrow for Arrow encoding.component_latency_seconds histogram and
component_latency_mean_seconds gauge internal metrics, exposing the time an
event spends in a single transform including the transform buffer.datadog_logs sink now defaults to zstd compression instead of no compression. This results in
better network efficiency and higher throughput. You can explicitly set compression = "none" to
restore the previous behavior of no compression, or set compression = "gzip" if you were previously
using gzip compression explicitly.content_encoding and cache_control options to the gcp_cloud_storage sink. content_encoding overrides the Content-Encoding header (defaults to the compression scheme’s content encoding). cache_control sets the Cache-Control header for created objects.websocket source performance by avoiding getting a new time for every event in an array.prometheus_remote_write sink now supports custom HTTP headers via the request.headers configuration option. This allows users to add custom headers to outgoing requests, which is useful for authentication, routing, or other integration requirements with Prometheus-compatible backends.internal_metrics.include_extended_tags configuration option
Added internal_metrics configuration section to the tag_cardinality_limit transform to better organize internal metrics configuration. The internal_metrics.include_extended_tags option controls whether to include extended tags (metric_name, tag_key) in the tag_value_limit_exceeded_total metric to help identify which specific metrics and tag keys are hitting the configured value limit. This option defaults to false because these tags have potentially unbounded cardinality.
tokio-util patch override and preserve recoverable decoding behavior via DecoderFramedRead.log_to_metric transform now correctly handles aggregated histogram and aggregated summary metrics./secrets/my-secrets/username)vector test printing literal \x1b escape codes instead of rendering ANSI colors when reporting VRL compilation errors.opentelemetry source now correctly uses Definition::any() for logs output schema when use_otlp_decoding is enabled.
Users can now enable schema validation for this source.default-no-vrl-cli feature flag, which did not control VRL CLI compilation.
This flag was equivalent to default without api-client and enrichment-tables.
Use default-no-api-client as a replacement (note: this includes enrichment-tables) or define custom features as needed.The *buffer_utilization_mean metrics have been enhanced to use time-weighted
averaging which make them more representative of the actual buffer utilization
over time.
This change is breaking due to the replacement of the existing
buffer_utilization_ewma_alpha config option with
buffer_utilization_ewma_half_life_seconds.
parse_yaml function. This function parses yaml according to the YAML 1.1 spec.authors: juchem (https://github.com/vectordotdev/vrl/pull/1602)
--quiet / -q flag to the CLI to suppress the banner text when starting the REPL.authors: thomasqueirozb (https://github.com/vectordotdev/vrl/pull/1617)
Before (generic E202 syntax error):
$ string("")
error[E202]: syntax error
┌─ :1:1
│
1 │ string("")
│ ^^^^^^^^^^^^ unexpected error: invalid escape character:
│
= see language documentation at https://vrl.dev
= try your code in the VRL REPL, learn more at https://vrl.dev/examples
After (correct E209 invalid escape character):
$ string("")
error[E209]: invalid escape character:
┌─ :1:10
│
1 │ string("")
│ ^ invalid escape character: a
│
= see language documentation at https://vrl.dev
= try your code in the VRL REPL, learn more at https://vrl.dev/examples
authors: thomasqueirozb (https://github.com/vectordotdev/vrl/pull/1579)
parse_duration panicked when large values overflowed during multiplication.
The function now returns an error instead.authors: thomasqueirozb (https://github.com/vectordotdev/vrl/pull/1618)
basename function to indicate that it can also return null.
Previously the type definition indicated that the function could only return bytes (or strings).authors: thomasqueirozb (https://github.com/vectordotdev/vrl/pull/1635)
Fixed incorrect parameter types in several stdlib functions:
md5: value parameter was typed as any, now correctly typed as bytes.
seahash: value parameter was typed as any, now correctly typed as bytes.
floor: value parameter was typed as any, now correctly typed as float | integer; precision parameter was typed as any, now correctly typed as integer.
parse_key_value: key_value_delimiter and field_delimiter parameters were typed as any, now correctly typed as bytes.
Note: the function documentation already reflected the correct types.
authors: thomasqueirozb (https://github.com/vectordotdev/vrl/pull/1650)
Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter