Vector v0.56.0 released on 03-06-2026
Vector v0.56.0 is out now. It delivers new ingestion and delivery features — a Databricks Zerobus sink, a delay transform, configurable HTTP retry behaviour, and zstd compression for Vector-to-Vector traffic.
See the full release notes on the Vector website or the project’s GitHub for installation instructions, examples, and configuration details.
What’s in this release
- databricks_zerobus sink for streaming logs to Databricks Unity Catalog tables (OAuth 2.0 authentication, automatic schema fetching, protobuf batch encoding).
- New delay transform to hold events by a fixed duration or conditionally using VRL; HTTP-based sinks gain a retry_strategy option to control which HTTP status codes trigger retries (with an http sink example).
- Major tag_cardinality_limit enhancements: per_tag_limits, tracking_scope: per_metric, a global max_tracked_keys cap, and the ability to opt entire metrics out of cardinality tracking.
Upgrade notes
- Breaking change: greptimedb_metrics and greptimedb_logs sinks now require GreptimeDB v1.x — upgrade your GreptimeDB instance before upgrading Vector if you use those sinks.
- Fixes and platform packaging: a CPU regression introduced in 0.50.0 has been fixed, and support for installing on RHEL 8 / Rocky Linux 8 / AlmaLinux 8 / CentOS Stream 8 has been restored; if you cannot upgrade GreptimeDB immediately, remain on your current Vector release until the database is updated.
Share comments or configuration notes on the release page or GitHub so others can learn from your experience and report any issues encountered.
