chore(deps): update timberio/vector docker tag to v0.58.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
timberio/vector	Component	minor	0.45.0-distroless-static → 0.58.0-distroless-static

---

Release Notes

vectordotdev/vector (timberio/vector)

v0.58.0

Compare Source

The COSE team is excited to announce version 0.58.0! 🚀

View release notes

v0.57.0

Compare Source

The COSE team is excited to announce version 0.57.0! 🚀

This is a security focused release which involves breaking changes, however we made sure to provide ways for users to restore previous behavior.

View release notes

v0.56.0

Compare Source

The COSE team is excited to announce version 0.56.0! 🚀

Release highlights

• Added a new databricks_zerobus sink that streams log data to Databricks Unity Catalog tables through the Zerobus ingestion service. The sink supports OAuth 2.0 authentication, automatic schema fetching from Unity Catalog, and protobuf batch encoding.
• Added a new delay transform that delays each event by a fixed duration. Events can also
  be delayed based on a condition which includes VRL transforms.
• HTTP-based sinks that use the shared retry helpers now support a retry_strategy configuration
  option to control which HTTP response codes are retried. The http sink also includes a new
  example showing how to retry only specific transient status codes.
• The vector sink now supports zstd compression in addition to gzip. This provides better
  compression ratios and performance for Vector-to-Vector communication.
• The tag_cardinality_limit transform received major enhancements: per-tag cardinality
  overrides (per_tag_limits), per-metric tracking isolation (tracking_scope: per_metric),
  a global key cap (max_tracked_keys), and the ability to opt entire metrics out of
  cardinality tracking.
• Parquet batch encoding in the aws_s3 sink is now available out of the box in official release
  binaries for all users.
• Fixed a CPU regression introduced in 0.50.0 affecting all sinks that use metric normalization such as prometheus_remote_write, aws_cloudwatch_metrics, statsd, and others.
• Restored support for installing Vector on RHEL 8, Rocky Linux 8, AlmaLinux 8, and CentOS
  Stream 8, which had been broken since 0.55.0 due to an inadvertent glibc requirement bump.
• Unit tests now support an optional expected_event_count field on test outputs, allowing assertions on the number of events emitted by a transform.

Breaking Changes

• The greptimedb_metrics and greptimedb_logs sinks now require GreptimeDB v1.x. Users running GreptimeDB v0.x must upgrade their GreptimeDB instance before upgrading Vector.

👉 View all new features and fixes in the release notes here.

v0.55.0

Compare Source

The COSE team is excited to announce version 0.55.0!

Release highlights

• New windows_event_log source that collects logs from Windows Event Log channels using the native Windows Event Log API, with pull-mode subscriptions, bookmark-based checkpointing, and configurable field filtering.
• The aws_s3 sink now supports Apache Parquet batch encoding. Events can be written as Parquet columnar files with either an auto-generated native schema or a supplied .schema file, and configurable compression (Snappy, ZSTD, GZIP, LZ4, or none).
• The azure_blob sink re-gains first-class Azure authentication: Azure CLI, Managed Identity, Workload Identity, and Managed Identity-based Client Assertion credential kinds are all supported again.
• The datadog_metrics sink now defaults to the Series v2 endpoint (/api/v2/series) and uses zstd compression for Series v2 and Sketches, which should yield smaller payloads and more efficient batching and intake. A new series_api_version option (v1 or v2) is available to opt back to the legacy v1 endpoint; Series v1 continues to use zlib.
• vector top is more trustworthy: per-output events for components with multiple output ports are now shown in the correct Events Out column, and the Memory Used column now reports disabled when the target Vector instance was started without --allocation-tracing instead of a misleading 0.
• Better internal metrics for capacity planning and alerting:
  • New source-send latency distributions (source_send_latency_seconds, source_send_batch_latency_seconds) surface backpressure close to the source.
  • Task-transform utilization no longer counts time spent waiting on downstream components, giving a more representative view of transform saturation.
  • Fixed a regression in buffer utilization metric tracking around underflow.
• Fixed a performance regression in the file and kubernetes_logs sources that could cause unexpectedly high CPU usage, introduced in 0.50.0.

Breaking Changes

See the 0.55 upgrade guide for full details and migration steps. At a glance, you are affected if you:

• query or tail the Vector observability API in any way: the API has moved from GraphQL to gRPC. This includes vector top, vector tap, and anything that talked to /graphql or the /playground. The HTTP GET /health endpoint is unchanged and continues to serve Kubernetes HTTP probes as before.
• set the top-level headers option on the http or opentelemetry sinks: it has been removed.
• use the azure_logs_ingestion sink with Client Secret credentials: azure_credential_kind must now be set explicitly.

View release notes

v0.54.0

Compare Source

The COSE team is excited to announce version 0.54.0! 🚀

Release highlights

• Enhanced vector top with new keybinds for scrolling, sorting, and filtering. Press ? to see all available keybindings.
• The datadog_logs sink now defaults to zstd compression instead of no compression, resulting in better network efficiency and higher throughput.
• Added component_latency_seconds histogram and component_latency_mean_seconds gauge internal metrics, exposing the time an event spends in a component.
• Syslog encoding transform received major upgrades with improved RFC compliance, support for scalars/nested objects/arrays in structured data, and better UTF-8 safety.
• Added a new 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).

Breaking Changes

• The datadog_logs sink now defaults to zstd compression. You can explicitly set compression to preserve previous behavior.

👉 View all new features and fixes in the release notes here.

v0.53.0

Compare Source

The COSE team is excited to announce version 0.53.0! 🚀

Release highlights

• Functions to access internal Vector metrics are now available for VRL: get_vector_metric, find_vector_metrics, and aggregate_vector_metrics. You are now able to fetch snapshots of the metrics that are updated every metrics_storage_refresh_period.
• The clickhouse sink now supports the arrow_stream format option, enabling high-performance binary data transfer using Apache Arrow IPC. This provides significantly better performance and smaller payload sizes compared to JSON-based formats.
• Added a new doris sink for sending log data to Apache Doris databases using the Stream Load API.
• Added syslog codec for encoding Vector events to Syslog format. RFC5424 and RFC3164 are supported.
• Added moving-mean gauges for source and transform buffers (source_buffer_utilization_mean and transform_buffer_utilization_mean), so observers can track an exponentially weighted moving average (EWMA) of buffer utilization in addition to the instant level.

👉 This release contains several more enhancements, bug fixes and breaking changes. View the full changelog here.

v0.52.0

Compare Source

The COSE team is excited to announce version 0.52.0! 🚀

Release highlights:

• Enhanced Vector’s observability with new buffer utilization metrics for sources and transforms (source_buffer_* and transform_buffer_* metrics), providing visibility into buffer capacity, usage and historical usage levels.
• Introduced trace_to_log transform that allows converting traces to logs.
• The blackhole sink now implements end-to-end acknowledgements.
• The GELF decoder now supports a validation option with two modes: strict (default) and relaxed. When set to relaxed, the decoder will parse GELF messages from sources that don’t strictly follow the GELF specification.
• The docker_logs source now retries Docker daemon communication failures with exponential backoff.

This release contains several more enhancements, bug fixes and breaking changes.

👉 View the full changelog here.

v0.51.1

Compare Source

The COSE team is excited to announce patch version 0.51.1 🚀

• This patch release addresses a number of internal logs rate limiting bugs.
• Also, the recently released VRL functions split_path, basename and dirname are now properly exposed.

If you are using v0.51.0, we recommend upgrading to this version.

👉 See the full changelog here: https://vector.dev/releases/0.51.1/

v0.51.0

Compare Source

[!CAUTION]
Please upgrade to https://github.com/vectordotdev/vector/releases/tag/v0.51.1 instead.

The COSE team is excited to announce version 0.51.0! 🚀

Release highlights:

• Enhanced OpenTelemetry Protocol (OTLP) support with the introduction of the otlp codec, enabling bidirectional conversion between Vector events and OTLP format for seamless integration with OpenTelemetry collectors and instrumentation.
• Improved Vector’s internal telemetry; fixed issues where utilization metrics reported negative values and buffer counters underflowed.
• Enhanced memory enrichment tables with an expired output for exporting expired cache items, and made enrichment table outputs accessible via vector tap.

This release contains several more enhancements, bug fixes and breaking changes.

👉 View the full changelog here.

v0.50.0

Compare Source

Datadog's Community Open Source team is excited to announce version 0.50.0 🚀

Changelog

View release notes

Release highlights

• The opentelemetry source can now decode data according to the standard OpenTelemetry protocolfor all telemetry data types (logs, metrics and traces). This eliminates the need for complex event remapping. It greatly simplifies configuration for OTEL -> Vector -> OTEL use cases or when forwarding data to any system that expects OTLP-formatted telemetry.
• A new varint_length_delimited framing option is now available which enables compatibility with standard protobuf streaming implementations and tools like ClickHouse.
• Introduced a new incremental_to_absolute transform, useful when metric data might be lost in transit or for creating a historical record of the metric.
• A new okta source for consuming Okta system logs is now available.
• The exec secrets option now supports protocol version v1.1 which can be used with the Datadog Secret Backend.

Breaking Changes

The azure_blob sink now requires a connection_string. This is the only supported authentication method for now. For more details, see this pull request.

v0.49.0

Compare Source

Datadog's Community Open Source team is excited to announce version 0.49.0 🚀

Here are some of the highlights from this release:

• A websocket source has been introduced. A WebSocket source in Vector enables ingestion of real-time data from services that expose WebSocket APIs.
• The http sink’s uri and request.headers config fields now support templating, allowing dynamic construction based on event data.
• The --watch-config flag now also watches for changes in enrichment table files.
• Added a TTL-based cache for metrics sets and also an expire_metrics_secs config option for the prometheus_remote_write sink. This fixes an issue where incremental metrics are preserved for the lifetime of Vector's runtime causing indefinite memory growth.
• Fixed a race condition that could cause negative values in the vector_buffer_byte_size and vector_buffer_events gauges.

A few VRL functions include breaking changes. Please refer to the upgrade guide for more details.

This release contains several more enhancements and bug fixes. View the full changelog here:
👉 https://vector.dev/releases/0.49.0/

v0.48.0

Compare Source

View release notes

v0.47.0

Compare Source

View release notes

v0.46.1

Compare Source

View release notes

v0.46.0

Compare Source

View release notes

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cla-assistant]

All committers have signed the CLA.