DEPRECATIONS - Vector

See DEPRECATION.md for the process for updating this file.

The format for each entry should be: <version> <identifier> <description>.

<version> should be the version of Vector in which to take the action (deprecate, migrate, or remove)
<identifier> should be a unique identifier that can also be used in the code to easily find the places to modify
<description> should be a longer form description of the change to be made

For example:

To be deprecated

v0.50.0 | http-server-encoding | The encoding field will be removed. Use decoding and framing instead.
v0.53.0 | buffer-bytes-events-metrics | The buffer_byte_size and buffer_events gauges are deprecated in favor of the buffer_size_bytes/buffer_size_events metrics described in docs/specs/buffer.md.
v0.58.0 | azure-monitor-logs-sink | The azure_monitor_logs sink is deprecated in favor of the new azure_logs_ingestion sink, which uses the Azure Monitor Logs Ingestion API. Users should migrate before Microsoft ends support for the old Data Collector API (scheduled for September 2026).
v0.57.0 | bool-or-vector-compression | The boolean syntax for the compression field in the vector sink (compression: true/compression: false) is deprecated. Use the string syntax instead (compression: "gzip", compression: "zstd", or compression: "none"). The bool_or_vector_compression deserializer should be removed once the boolean syntax is no longer supported.
v0.58.0 | datadog-metrics-series-v1 | The series_api_version: v1 option on the datadog_metrics sink is deprecated in favor of v2 (the default). The v1 series endpoint (/api/v1/series) is a legacy endpoint; users should remove series_api_version: v1 from their configuration or set it to v2.

v0.56.0 | greptimedb-v0-support | The greptimedb_metrics and greptimedb_logs sinks drop support for GreptimeDB v0.x. Users must upgrade their GreptimeDB instance to v1.x before upgrading Vector.