Deprecations
See the deprecation policy for details.
Active Deprecations
The current Vector release is v0.62.0. Deprecations become eligible for removal two minor versions after their announcement.
- Configuring a PKCS#12 archive via
tls.key_fileinamqpsource and sinkConfiguring a PKCS#12 archive via
tls.key_filein theamqpsource and sink is deprecated. Pass the archive viatls.crt_fileinstead.Migrate by replacing:
sinks: # or sources my_amqp: type: amqp tls: key_file: "/path/to/identity.p12"with:
sinks: # or sources my_amqp: type: amqp tls: crt_file: "/path/to/identity.p12"Deprecated in v0.62.0 connection_send_errors_totalmetricThe
connection_send_errors_totalcounter emitted by UDP sinks, such as thesocketandstatsdsinks inudpmode, is deprecated. Use thecomponent_errors_totalmetric instead.Migrate any dashboards or alerts that reference:
connection_send_errors_total{mode="udp"}
to:
component_errors_total{component_kind="sink", error_type="writer_failed", stage="sending"}
The replacement does not include the
modelabel. Remove that selector from existing queries and keep any component-specific selectors, such ascomponent_idorcomponent_type.There is no exact one-to-one replacement. With these selectors,
component_errors_totalalso counts other sink send failures, such as UDP chunking errors and socket send errors.Deprecated in v0.62.0- Datadog Agent source
disable_*configuration optionsThe
datadog_agentsource’sdisable_logs,disable_metrics,disable_traces, anddisable_llmobsoptions are deprecated. Switch toenabled_data_typesand list the data types the source accepts.For example, replace:
disable_metrics: true disable_traces: true disable_llmobs: truewith:
enabled_data_types: ["logs"]Existing settings still work, but produce a deprecation warning.
When migrating:
- Leave out
enabled_data_typesto accept all data types exceptapm_stats. - Use the data type names
logs,metrics,traces, andllmobs. Whenmultiple_outputsis enabled, each data type is sent to the output of the same name. - Remove all
disable_*options when addingenabled_data_types. If both are set, data types disabled bydisable_*are removed fromenabled_data_types.
Deprecated in v0.62.0 - Leave out
- Google Cloud Storage sink
api_keyconfiguration optionThe
api_keyconfiguration option for the Google Cloud Storage sink is deprecated. Google Cloud Storage does not support API keys for authentication.Migration:
- Remove the
api_keyoption from your configuration. - To authenticate, use one of the methods:
- Specify the path to a service account credentials using the
credentials_pathconfiguration option. - Set the
GOOGLE_APPLICATION_CREDENTIALSenvironment variable pointing to your credentials file. - Rely on automatic credentials discovery when running on a GCE instance.
- Specify the path to a service account credentials using the
Deprecated in v0.62.0 - Remove the
metadata_refresh_failed_totalmetricThe
metadata_refresh_failed_totalcounter emitted by theaws_ec2_metadatatransform is deprecated. Use thecomponent_errors_totalmetric instead.Migrate any dashboards or alerts that reference:
metadata_refresh_failed_total
to:
component_errors_total{component_type="aws_ec2_metadata", error_type="request_failed", stage="processing"}
Keep these selectors, and any existing
component_idselector, so that the query does not count errors from unrelated components.Deprecated in v0.62.0- APT/YUM repository configuration that trusts only Datadog signing keys
On November 30, 2026, Vector’s APT and YUM repositories switch to a new signing key. To continue installing or updating packages after that date, add the new key.
On each host that you configured with
setup.vector.dev, run the following commands before November 30, 2026. The script adds the new key and keeps your repository URL, channel, and existing trusted keys:curl -fsSL --proto '=https' --proto-redir '=https' \ https://install.datadoghq.com/vector/setup.sh \ -o vector-setup.sh && bash vector-setup.sh --migrateAfter the switch, refresh repository metadata and upgrade Vector:
# Debian / Ubuntu sudo apt-get update && sudo apt-get install --only-upgrade vector# RPM systems sudo dnf --refresh upgrade vector # If dnf is unavailable: sudo yum clean metadata && sudo yum update vectorFor custom source layouts, add the new public key to the keyrings referenced by APT’s
Signed-Byor to YUM/DNF’sgpgkeyconfiguration, keeping existing trusted keys.Deprecated in v0.62.0 - Ignored configuration fields
Configuration fields that Vector accepts but discards during deserialization are deprecated. Vector now warns about these fields when loading configuration, including during
vector validate. Existing configurations continue to work.Correct misspelled fields or remove fields that do not belong to the selected enum variant. For example, replace this HTTP sink request setting:
request: retry_atempts: 3with:
request: retry_attempts: 3For options that select an enum variant, keep only the fields used by that variant. For example, HTTP authentication with
strategy: bearerusestoken. Removeusernameandpassword, which belong to thebasicvariant:auth: strategy: bearer token: example-tokenWarnings identify field paths without including their values. Maps that accept arbitrary keys, such as HTTP headers, remain supported. Recognized settings documented as inactive in a particular mode, such as
value_limitwithmode: excludedintag_cardinality_limit, are not affected by this deprecation.Deprecated in v0.61.0 - Boolean shorthand for object-valued configuration options
Boolean shorthand for object-valued configuration options is deprecated. Use the object form instead so that each setting has one consistent representation and the options being configured are explicit.
Existing boolean values continue to work. Removal is not yet scheduled. We will give users at least one month to migrate before removing this shorthand.
This applies to
healthcheckon sinks, global and sinkacknowledgements,jetstreamon the NATS sink, andacknowledgementson the Splunk HEC source. Ordinary boolean options, such ashealthcheck.enabled, are unaffected.Please also see the dedicated note for
use_otlp_decoding.Settings with an
enabledfieldFor
healthcheck, global and sinkacknowledgements, NATS sinkjetstream, and Splunk HEC sourceacknowledgements, replace the boolean with an object containing the same value inenabled. For example, within a sink configuration, replace:healthcheck: false acknowledgements: truewith:
healthcheck: enabled: false acknowledgements: enabled: trueOther options in these objects retain their defaults. Use the same transformation for either
trueorfalse.Deprecated in v0.60.0 - OpenTelemetry
use_otlp_decodingconfiguration optionThe
opentelemetrysource’suse_otlp_decodingoption is deprecated. Switch todecodingwithcodec: otlpto preserve the same behavior asuse_otlp_decoding: true.To preserve the OTLP representation of all signals, replace:
use_otlp_decoding: truewith:
decoding: codec: otlpTo preserve OTLP only for selected signals, replace:
use_otlp_decoding: logs: false metrics: false traces: truewith:
decoding: codec: otlp signal_types: ["traces"]Existing boolean and object settings still work, but produce a deprecation warning.
When migrating:
- Leave out
signal_typesto keep all signals in OTLP format. Any types not included will remain in Vector’s native format. - If you currently use
use_otlp_decoding: false, remove it and leave outdecoding. Native conversion remains the default. - Use
codec: otlpand the signal nameslogs,metrics, andtraces. Other values are not supported. - Remove
use_otlp_decodingwhen addingdecoding. Setting both prevents Vector from starting.
Deprecated in v0.60.0 - Leave out
aggregate_failed_updatescounter without the_totalsuffixThe
aggregatetransform now also emits the failed-updates counter with the_totalsuffix, matching Vector’s counter naming convention:aggregate_failed_updates_total
The previous name without the
_totalsuffix is deprecated and will be removed in a future release. Migrate any dashboards or alerts that reference:aggregate_failed_updates
Deprecated in v0.59.0- legacy memory enrichment table counters without the
_totalsuffixThe memory enrichment table failure and TTL-expiration counters are now also emitted with the
_totalsuffix, matching Vector’s counter naming convention:memory_enrichment_table_failed_insertions_totalmemory_enrichment_table_failed_reads_totalmemory_enrichment_table_ttl_expirations_total
The previous names without the
_totalsuffix are deprecated and will be removed in a future release. Migrate any dashboards or alerts that reference:memory_enrichment_table_failed_insertionsmemory_enrichment_table_failed_readsmemory_enrichment_table_ttl_expirations
Deprecated in v0.59.0 - Stable Vector artifacts hosted at
packages.timber.ioStable Vector release archives and packages are now hosted in the public COSE release bucket. The
packages.timber.io/vectorURLs are deprecated and users should switch toinstall.datadoghq.com/vectorinstead.Starting with Vector
0.59.0, the Vector installer and the download instructions on vector.dev point to artifacts in the COSE bucket. Existingpackages.timber.ioURLs continue to work during the deprecation period.Artifact Migration outcome Stable Vector releases, installers, and package-manager downloads Migrated to exact-version paths under install.datadoghq.com/vector/<version>/; stablelatestor.Xaliases are not providedpackages.timber.io/vectorversioned,latest, and version-alias URLsRemain readable through December 31, 2026, and may be deleted at any time after that date Nightly and custom builds Treated as transient artifacts that are superseded by stable releases, so existing builds are not migrated; future builds are published to install.datadoghq.comundervector/nightly/andvector/custom/Helm charts GitHub Release assets; https://helm.vector.devremains the Helm repository indexAll other legacy artifacts Not migrated and will be deleted Deprecated in v0.59.0
Past Deprecations
These features have been removed from Vector as of version v0.62.0.
- host
process_runtimecounter without the_totalsuffixThe
host_metricssource now also emits the process runtime counter with the_totalsuffix, matching Vector’s counter naming convention:process_runtime_total
The previous name without the
_totalsuffix is deprecated and will be removed in a future release. Migrate any dashboards or alerts that reference:process_runtime
- Environment-variable and secret placeholders in non-string positions
As of 0.62.0, Vector parses configuration files before substituting
${VAR}andSECRET[backend.key]references. Substituted values cannot change the configuration structure.Quote placeholders in TOML and JSON values and in YAML flow collections. Use literal map keys, component names, and table headers. Replace placeholders that expanded into configuration fragments or multiple array elements with explicit configuration. String substitutions, including values converted to numeric or boolean fields, remain supported.
Environment-variable interpolation remains disabled by default. Enable it with
--dangerously-allow-env-var-interpolationorVECTOR_DANGEROUSLY_ALLOW_ENV_VAR_INTERPOLATION=true.See the environment-variable documentation and secrets documentation for migration guidance.
buffer_max_byte_sizeandbuffer_max_event_sizegauge metricsThe buffer maximum-size gauges were renamed to follow Vector’s metric naming standard. The legacy names are still emitted, but they are deprecated and will be removed in a future release.
Migrate any dashboards or alerts that reference:
buffer_max_byte_sizebuffer_max_event_sizesource_buffer_max_byte_sizesource_buffer_max_event_sizetransform_buffer_max_byte_sizetransform_buffer_max_event_size
to:
buffer_max_size_bytesbuffer_max_size_eventssource_buffer_max_size_bytessource_buffer_max_size_eventstransform_buffer_max_size_bytestransform_buffer_max_size_events
internal_metrics_cardinality_totalcounter metricThe
internal_metrics_cardinality_totalcounter emitted by theinternal_metricssource is deprecated. Use theinternal_metrics_cardinalitygauge instead.Both metrics report the same value: the current number of metrics in the registry. When
expire_metrics_secsis set, the registry expires metrics and this value can decrease. A counter must not decrease, so consumers that expect counter semantics can misinterpretinternal_metrics_cardinality_total.Migrate any dashboards or alerts that reference:
internal_metrics_cardinality_total
to:
internal_metrics_cardinality
- scheme-less
addressandrouting.endpointsvalues in thevectorsink defaulting tohttpA
vectorsink endpoint such as127.0.0.1without an explicit scheme currently defaults tohttp. This behavior is deprecated and will change tohttpsin a future release. Note that when TLS is enabled, a scheme-less address already defaults tohttps.Migrate by specifying the scheme explicitly:
sinks: my_sink: type: vector address: http://127.0.0.1:6000 - omitting the
versionfield oninfluxdb_logsandinfluxdb_metricssinksThe
versionfield selects the InfluxDB API version whose settings are used. It will be required in a future release. Until then, whenversionis unset the version is inferred from the configured settings.version: "1"uses the v1 settings:database,consistency,retention_policy_name,username, andpassword.version: "2"uses the v2 settings:org,bucket, andtoken.
Migrate by adding
version: "1"orversion: "2"to match the settings already present:sinks: my_sink: type: influxdb_logs version: "2" org: my-org bucket: vector-bucket token: ${INFLUXDB_TOKEN} series_api_version: v1option on thedatadog_metricssinkThe
series_api_version: v1option is deprecated in favor ofv2(the default). The v1 series endpoint (/api/v1/series) is a legacy endpoint.Users should remove
series_api_version: v1from their configuration or set it tov2.- Boolean syntax for the
compressionfield in thevectorsinkThe boolean syntax (
compression: true/compression: false) is deprecated. Use the string syntax instead:compression: "gzip",compression: "zstd", orcompression: "none".The
bool_or_vector_compressiondeserializer will be removed once the boolean syntax is no longer supported. azure_monitor_logssinkThe
azure_monitor_logssink is deprecated in favor of the newazure_logs_ingestionsink, 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).
buffer_byte_sizeandbuffer_eventsgauge metricsThe
buffer_byte_sizeandbuffer_eventsgauges are deprecated in favor of thebuffer_size_bytesandbuffer_size_eventsmetrics.encodingfield on HTTP server sourcesThe
encodingfield will be removed. Usedecodingandframinginstead.- GreptimeDB v0.x support in
greptimedb_metricsandgreptimedb_logssinksThe
greptimedb_metricsandgreptimedb_logssinks drop support for GreptimeDB v0.x. Users must upgrade their GreptimeDB instance to v1.x before upgrading Vector.