Vector | v0.54.0

Vector v0.54.0 released on 10-03-2026


Vector v0.54.0 is out now. Enhanced “vector top” adds interactive keybindings for scrolling, sorting and filtering, making it quicker to navigate and inspect runtime metrics.

Visit the project’s GitHub release notes or the official Vector documentation for full details and configuration examples.

What’s in this release

  • Improved “vector top” UI with new keybindings (press “?” in the UI to view available keybindings) for faster navigation, sorting and filtering of runtime metrics.
  • The datadog_logs sink now defaults to zstd compression (previously no compression) to reduce network usage and increase throughput.
  • New internal metrics: component_latency_seconds (histogram) and component_latency_mean_seconds (gauge) to expose how long events spend inside individual components.
  • Syslog encoding received RFC-compliance and UTF‑8 safety improvements, plus a new azure_logs_ingestion sink; the existing azure_monitor_logs sink is deprecated.

Upgrade notes

  • Behavioral breaking change: datadog_logs now defaults to zstd. If you need the previous uncompressed behaviour, explicitly set the sink’s compression option to preserve it.
  • Migration note: the azure_monitor_logs sink is deprecated. Plan migration to azure_logs_ingestion before Microsoft ends the old Data Collector API (scheduled for September 2026); to revert short-term, pin to an earlier Vector release.

Share your experience or any issues you encounter with the release — the community will appreciate practical feedback on the new UI and sinks.

Related posts

Agentic AI still needs domain judgement

Agentic AI can write the thing, but it still cannot tell you whether the thing is right. That is where domain expertise matters, because a clean config or neat bit of glue logic can still be wrong in...

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...