APT and YUM package repositories will use a new signing key on November 30, 2026. Migration instructions

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_file in amqp source and sink

    Configuring a PKCS#12 archive via tls.key_file in the amqp source and sink is deprecated. Pass the archive via tls.crt_file instead.

    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_total metric

    The connection_send_errors_total counter emitted by UDP sinks, such as the socket and statsd sinks in udp mode, is deprecated. Use the component_errors_total metric 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 mode label. Remove that selector from existing queries and keep any component-specific selectors, such as component_id or component_type.

    There is no exact one-to-one replacement. With these selectors, component_errors_total also counts other sink send failures, such as UDP chunking errors and socket send errors.

    Deprecated in v0.62.0
  • Datadog Agent source disable_* configuration options

    The datadog_agent source’s disable_logs, disable_metrics, disable_traces, and disable_llmobs options are deprecated. Switch to enabled_data_types and list the data types the source accepts.

    For example, replace:

    disable_metrics: true
    disable_traces: true
    disable_llmobs: true
    

    with:

    enabled_data_types: ["logs"]
    

    Existing settings still work, but produce a deprecation warning.

    When migrating:

    • Leave out enabled_data_types to accept all data types except apm_stats.
    • Use the data type names logs, metrics, traces, and llmobs. When multiple_outputs is enabled, each data type is sent to the output of the same name.
    • Remove all disable_* options when adding enabled_data_types. If both are set, data types disabled by disable_* are removed from enabled_data_types.
    Deprecated in v0.62.0
  • Google Cloud Storage sink api_key configuration option

    The api_key configuration option for the Google Cloud Storage sink is deprecated. Google Cloud Storage does not support API keys for authentication.

    Migration:

    1. Remove the api_key option from your configuration.
    2. To authenticate, use one of the methods:
      • Specify the path to a service account credentials using the credentials_path configuration option.
      • Set the GOOGLE_APPLICATION_CREDENTIALS environment variable pointing to your credentials file.
      • Rely on automatic credentials discovery when running on a GCE instance.
    Deprecated in v0.62.0
  • metadata_refresh_failed_total metric

    The metadata_refresh_failed_total counter emitted by the aws_ec2_metadata transform is deprecated. Use the component_errors_total metric 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_id selector, 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 --migrate
    

    After 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 vector
    

    For custom source layouts, add the new public key to the keyrings referenced by APT’s Signed-By or to YUM/DNF’s gpgkey configuration, 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: 3
    

    with:

    request:
      retry_attempts: 3
    

    For options that select an enum variant, keep only the fields used by that variant. For example, HTTP authentication with strategy: bearer uses token. Remove username and password, which belong to the basic variant:

    auth:
      strategy: bearer
      token: example-token
    

    Warnings 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_limit with mode: excluded in tag_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 healthcheck on sinks, global and sink acknowledgements, jetstream on the NATS sink, and acknowledgements on the Splunk HEC source. Ordinary boolean options, such as healthcheck.enabled, are unaffected.

    Please also see the dedicated note for use_otlp_decoding.

    Settings with an enabled field

    For healthcheck, global and sink acknowledgements, NATS sink jetstream, and Splunk HEC source acknowledgements, replace the boolean with an object containing the same value in enabled. For example, within a sink configuration, replace:

    healthcheck: false
    acknowledgements: true
    

    with:

    healthcheck:
      enabled: false
    acknowledgements:
      enabled: true
    

    Other options in these objects retain their defaults. Use the same transformation for either true or false.

    Deprecated in v0.60.0
  • OpenTelemetry use_otlp_decoding configuration option

    The opentelemetry source’s use_otlp_decoding option is deprecated. Switch to decoding with codec: otlp to preserve the same behavior as use_otlp_decoding: true.

    To preserve the OTLP representation of all signals, replace:

    use_otlp_decoding: true
    

    with:

    decoding:
      codec: otlp
    

    To preserve OTLP only for selected signals, replace:

    use_otlp_decoding:
      logs: false
      metrics: false
      traces: true
    

    with:

    decoding:
      codec: otlp
      signal_types: ["traces"]
    

    Existing boolean and object settings still work, but produce a deprecation warning.

    When migrating:

    • Leave out signal_types to 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 out decoding. Native conversion remains the default.
    • Use codec: otlp and the signal names logs, metrics, and traces. Other values are not supported.
    • Remove use_otlp_decoding when adding decoding. Setting both prevents Vector from starting.
    Deprecated in v0.60.0
  • aggregate_failed_updates counter without the _total suffix

    The aggregate transform now also emits the failed-updates counter with the _total suffix, matching Vector’s counter naming convention:

    • aggregate_failed_updates_total

    The previous name without the _total suffix 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 _total suffix

    The memory enrichment table failure and TTL-expiration counters are now also emitted with the _total suffix, matching Vector’s counter naming convention:

    • memory_enrichment_table_failed_insertions_total
    • memory_enrichment_table_failed_reads_total
    • memory_enrichment_table_ttl_expirations_total

    The previous names without the _total suffix are deprecated and will be removed in a future release. Migrate any dashboards or alerts that reference:

    • memory_enrichment_table_failed_insertions
    • memory_enrichment_table_failed_reads
    • memory_enrichment_table_ttl_expirations
    Deprecated in v0.59.0
  • Stable Vector artifacts hosted at packages.timber.io

    Stable Vector release archives and packages are now hosted in the public COSE release bucket. The packages.timber.io/vector URLs are deprecated and users should switch to install.datadoghq.com/vector instead.

    Starting with Vector 0.59.0, the Vector installer and the download instructions on vector.dev point to artifacts in the COSE bucket. Existing packages.timber.io URLs continue to work during the deprecation period.

    ArtifactMigration outcome
    Stable Vector releases, installers, and package-manager downloadsMigrated to exact-version paths under install.datadoghq.com/vector/<version>/; stable latest or .X aliases are not provided
    packages.timber.io/vector versioned, latest, and version-alias URLsRemain readable through December 31, 2026, and may be deleted at any time after that date
    Nightly and custom buildsTreated as transient artifacts that are superseded by stable releases, so existing builds are not migrated; future builds are published to install.datadoghq.com under vector/nightly/ and vector/custom/
    Helm chartsGitHub Release assets; https://helm.vector.dev remains the Helm repository index
    All other legacy artifactsNot 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_runtime counter without the _total suffix

    The host_metrics source now also emits the process runtime counter with the _total suffix, matching Vector’s counter naming convention:

    • process_runtime_total

    The previous name without the _total suffix is deprecated and will be removed in a future release. Migrate any dashboards or alerts that reference:

    • process_runtime
    Deprecated in v0.59.0 · Removed in v0.62.0
  • Environment-variable and secret placeholders in non-string positions

    As of 0.62.0, Vector parses configuration files before substituting ${VAR} and SECRET[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-interpolation or VECTOR_DANGEROUSLY_ALLOW_ENV_VAR_INTERPOLATION=true.

    See the environment-variable documentation and secrets documentation for migration guidance.

    Deprecated in v0.57.0 · Removed in v0.62.0
  • buffer_max_byte_size and buffer_max_event_size gauge metrics

    The 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_size
    • buffer_max_event_size
    • source_buffer_max_byte_size
    • source_buffer_max_event_size
    • transform_buffer_max_byte_size
    • transform_buffer_max_event_size

    to:

    • buffer_max_size_bytes
    • buffer_max_size_events
    • source_buffer_max_size_bytes
    • source_buffer_max_size_events
    • transform_buffer_max_size_bytes
    • transform_buffer_max_size_events
    Deprecated in v0.53.0 · Removed in v0.62.0
  • internal_metrics_cardinality_total counter metric

    The internal_metrics_cardinality_total counter emitted by the internal_metrics source is deprecated. Use the internal_metrics_cardinality gauge instead.

    Both metrics report the same value: the current number of metrics in the registry. When expire_metrics_secs is set, the registry expires metrics and this value can decrease. A counter must not decrease, so consumers that expect counter semantics can misinterpret internal_metrics_cardinality_total.

    Migrate any dashboards or alerts that reference:

    • internal_metrics_cardinality_total

    to:

    • internal_metrics_cardinality
    Deprecated in v0.24.0 · Removed in v0.62.0
  • scheme-less address and routing.endpoints values in the vector sink defaulting to http

    A vector sink endpoint such as 127.0.0.1 without an explicit scheme currently defaults to http. This behavior is deprecated and will change to https in a future release. Note that when TLS is enabled, a scheme-less address already defaults to https.

    Migrate by specifying the scheme explicitly:

    sinks:
      my_sink:
        type: vector
        address: http://127.0.0.1:6000
    
    Deprecated in v0.59.0 · Removed in v0.61.0
  • omitting the version field on influxdb_logs and influxdb_metrics sinks

    The version field selects the InfluxDB API version whose settings are used. It will be required in a future release. Until then, when version is unset the version is inferred from the configured settings.

    • version: "1" uses the v1 settings: database, consistency, retention_policy_name, username, and password.
    • version: "2" uses the v2 settings: org, bucket, and token.

    Migrate by adding version: "1" or version: "2" to match the settings already present:

    sinks:
      my_sink:
        type: influxdb_logs
        version: "2"
        org: my-org
        bucket: vector-bucket
        token: ${INFLUXDB_TOKEN}
    
    Deprecated in v0.58.0 · Removed in v0.60.0
  • series_api_version: v1 option on the datadog_metrics sink

    The series_api_version: v1 option 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.

    Deprecated in v0.56.0 · Removed in v0.60.0
  • Boolean syntax for the compression field in the vector sink

    The boolean syntax (compression: true / compression: false) is deprecated. Use the string syntax instead: compression: "gzip", compression: "zstd", or compression: "none".

    The bool_or_vector_compression deserializer will be removed once the boolean syntax is no longer supported.

    Deprecated in v0.56.0 · Removed in v0.59.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).

    Deprecated in v0.54.0 · Removed in v0.58.0
  • buffer_byte_size and buffer_events gauge metrics

    The buffer_byte_size and buffer_events gauges are deprecated in favor of the buffer_size_bytes and buffer_size_events metrics.

    Deprecated in v0.53.0 · Removed in v0.58.0
  • encoding field on HTTP server sources

    The encoding field will be removed. Use decoding and framing instead.

    Deprecated in v0.50.0 · Removed in v0.58.0
  • GreptimeDB v0.x support in greptimedb_metrics and greptimedb_logs sinks

    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.

    Deprecated in v0.55.0 · Removed in v0.56.0