Vector v0.62.0 release notes

Upgrading Vector
When upgrading, we recommend stepping through minor versions as these can each contain breaking changes while Vector is pre-1.0. These breaking changes are noted in their respective upgrade guides. Read the upgrade guide for this release.

The COSE team is happy to announce Vector 0.62.0! 🚀

Thanks to the 18 contributors who made the 40 changes in this release:

Upgrading to 0.62? Read the upgrade guide.

Vector Changelog

6 breaking changes

  • Absent histogram sums are no longer reported as zero
    A histogram’s sum is now optional, so a source that reports no sum no longer has one fabricated as zero. OTLP makes sum optional and OpenMetrics only recommends the _sum series, so the opentelemetry and prometheus_* sources can produce histograms without one. Downstream the sum is omitted rather than reported as zero: the prometheus_exporter and prometheus_remote_write sinks skip the <name>_sum series, influxdb_metrics omits the sum field, greptimedb_metrics omits the sum column, and a lua transform sees aggregated_histogram.sum as nil.
    Thanks to gwenaskell for contributing PR #25752!
  • internal_metrics_cardinality_total counter removed
    The internal_metrics source no longer emits the internal_metrics_cardinality_total counter. It was deprecated in 0.24.0 in favor of the internal_metrics_cardinality gauge, which reports the same value: the current number of metrics in the registry.
    Thanks to JinchengCao for contributing PR #27074!
  • Legacy buffer maximum-size metrics removed
    The deprecated buffer_max_byte_size, buffer_max_event_size, source_buffer_max_byte_size, source_buffer_max_event_size, transform_buffer_max_byte_size, and transform_buffer_max_event_size gauge metrics have been removed. They were deprecated in 0.53.0 in favor of the *_max_size_bytes and *_max_size_events gauges, which report the same values.
    Thanks to JinchengCao for contributing PR #27076!
  • Legacy process_runtime counter removed
    The host_metrics source no longer emits the process_runtime counter. It was deprecated in 0.59.0 in favor of process_runtime_total, which reports the same value with the same tags.
    Thanks to JinchengCao for contributing PR #27073!
  • The mongodb_metrics source requires MongoDB 4.4 or newer
    The mongodb driver is updated to 3.9.1, which removes support for MongoDB 4.2. The mongodb_metrics source now requires MongoDB server 4.4 or newer (wire version 9 or newer). Connections to MongoDB 4.2 or older servers now fail with an incompatible server error. MongoDB 4.2 reached end of life on April 30, 2023.
    Thanks to thomasqueirozb for contributing PR #26878!
  • Configuration is parsed before interpolation

    Vector now parses configuration files before substituting environment variables and SECRET[backend.key] references. Substitution applies only to string values, followed by conversion to the field’s declared type. Quotes, newlines, and other configuration syntax in substituted values cannot add keys, components, or array elements.

    This removes structural interpolation, deprecated in 0.57.0. Environment-variable interpolation remains disabled by default and still requires --dangerously-allow-env-var-interpolation or VECTOR_DANGEROUSLY_ALLOW_ENV_VAR_INTERPOLATION=true.

    Thanks to pront for contributing PR #26475!

3 new features

  • Added a GetCapabilities RPC to the Vector observability gRPC API. Clients such as vector top can call this once at connection time to discover whether allocation tracing is active and the full set of metric names (counters, gauges, histograms) available on the running instance.
    Thanks to thomasqueirozb for contributing PR #25427!
  • The datadog_agent source now accepts apm_stats (alpha) in enabled_data_types, which emits the APM stats sent by the Datadog Agent unmodified on a new apm_stats output instead of dropping them. It requires multiple_outputs and is not enabled when enabled_data_types is omitted.
    Thanks to antoninferrand for contributing PR #26940!
  • Added MessagePack decoder codec message_pack.

    Stream-based socket sources (tcp and unix_stream modes) require an explicit framing method when using message_pack.

    Thanks to Keuin, byronwolfman for contributing PR #27119!

8 enhancements

  • The aggregate transform now supports an event_time.late_events option to control metrics that arrive after their bucket’s cutoff. Setting strategy to forward sends them downstream unchanged instead of dropping them, and the optional metric_types list restricts forwarding to incremental metrics of the listed types (for example distribution and sketch). The default strategy, drop, keeps the existing behavior.
    Thanks to dd-sebastien-lb for contributing PR #27045!
  • Adds multi-value tags support for log_to_metric transform when using all_metrics: true.
    Thanks to tchanturia for contributing PR #27103!
  • The datadog_agent source now supports an enabled_data_types option that lists the data types (logs, metrics, traces, llmobs) the source accepts. This replaces the (now deprecated) disable_logs, disable_metrics, disable_traces, and disable_llmobs options. Please see the dedicated migration notice.
    Thanks to antoninferrand for contributing PR #27000!
  • The datadog_traces sink now supports a disable_apm_stats option, which stops the sink from computing APM stats from the traces it receives, for example when the Datadog Agent’s stats are forwarded separately.
    Thanks to antoninferrand for contributing PR #26939!
  • HTTP-based sinks now accept UTF-8 characters in the path or query of their endpoint URI, for example https://example.com/café?tag=é. Before, such an endpoint failed with invalid uri character. Hosts must still be ASCII, so use the punycode form of an internationalized domain name.

    The same change applies to the endpoints of the http_client, prometheus_scrape, apache_metrics, nginx_metrics, eventstoredb_metrics and aws_ecs_metrics sources, and to the endpoint and tags options of the aws_ec2_metadata transform. The http_client and prometheus_scrape sources percent-encode the query string before they send the request.

    This does not apply to the http sink’s uri, the opentelemetry sink’s protocol.uri, or the axiom sink’s url. Vector treats these as templates, and they must still contain only ASCII characters, both as written in the config and after event fields are filled in.

    Thanks to thomasqueirozb for contributing PRs #27012, #26977!
  • The internal_metrics source has a new emit_incremental option that emits counters and histograms as increments since the previous scrape instead of absolute totals. This keeps sinks like datadog_metrics from dropping histograms observed within a single scrape interval and the first scrape of each counter.
    Thanks to gwenaskell for contributing PR #26080!
  • Retry logs now include the retry attempt number. Sustained retryable sink failures are logged at error level every 10 attempts so persistent destination outages can trigger monitoring.
    Thanks to 20agbekodo for contributing PR #27081!
  • The remap transform can now change a metric’s type between counter and gauge by assigning to .type, for example .type = "counter". The metric’s value and kind are kept. This is useful when a source can’t tell a metric’s type, such as Prometheus remote write samples that arrive without type metadata and default to gauges.

    Like other disallowed metric changes, assigning any other value to .type, or changing the type of a set, distribution, histogram, summary, or sketch metric, is ignored and leaves the metric unchanged.

    Thanks to sghall for contributing PR #27080!

23 bug fixes

  • Fixed mutual TLS (mTLS) authentication by properly passing client certificates in the amqp source and sink.

    A configuration that specifies both tls.crt_file and a PKCS#12 archive in tls.key_file now fails, because that setup contradicts the documented TLS configuration. For more information, see the amqp source docs and amqp sink docs.

    Thanks to Captain1653 for contributing PR #27130!
  • Fixed an issue in the amqp sink where configuring a DER or inline PEM certificate in tls.ca_file caused initialization errors.
    Thanks to Captain1653 for contributing PR #27100!
  • The http_client source now sends Accept: application/json when decoding.codec is json, native_json or gelf and the default bytes framing is used. Previously it sent Accept: text/plain.
    Thanks to anpawo for contributing PR #27147!
  • Messages that are not valid UTF-8 no longer fail octet_counting, the framing the syslog source uses, in either its octet-counted or newline-delimited mode. UTF-8 handling is now done by the configured deserializer. syslog decoding replaces invalid sequences with U+FFFD by default (lossy). Because framing no longer errors, the syslog source no longer closes a connection that carried a non UTF-8 message. Previously the framing error ended the connection, losing every message after it on that connection.
    Thanks to yackushevas for contributing PR #26993!
  • The log_to_metric transform with all_metrics: true now accepts integer values wherever it expects a float (for example counter.value, gauge.value, histogram upper_limit and sum, summary quantile, value and sum). Previously a value such as 42 was rejected with a “Failed to parse field as float” error and the event was dropped, while 42.0 worked.
    Thanks to anpawo for contributing PR #27142!
  • vector tap now exits cleanly when its output pipe is closed, for example vector tap | head -1, instead of panicking with “failed printing to stdout: Broken pipe”.
    Thanks to anpawo for contributing PR #27146!
  • Fixed sum/avg reported by the DDSketch generated when converting an AggregatedHistogram (used by the datadog_metrics sink, among others). Both were previously reconstructed purely from bucket-boundary interpolation, which breaks down badly when a bucket’s true values sit far from its edges. sum/avg are now taken directly from the histogram’s own exact running totals instead (skipped if the buckets don’t fully account for the histogram’s true count — e.g. Prometheus dropping its cumulative +Inf bucket — or if that exact sum is not a finite number).
    Thanks to vladimir-dd, gwenaskell for contributing PR #25752!
  • The sketch conversion used by the datadog_metrics sink no longer reports a sum and average of zero for a histogram that reports no sum, keeping its bucket-derived estimate instead. Previously such a histogram arrived with a fabricated sum of zero, which the conversion then trusted as exact.
    Thanks to gwenaskell for contributing PR #25752!
  • The remap transform’s “Event mapping aborted.” debug log now includes the message given to abort in its error field, so the reason for a dropped event is no longer lost when reroute_dropped is not enabled.
    Thanks to anpawo for contributing PR #27148!
  • The mqtt source now subscribes to its topics again after reconnecting when the broker reports that the session is no longer present (for example after a broker restart, an expired session, or a deleted subscription queue). Previously the source stayed connected but silently stopped receiving messages until Vector was restarted.
    Thanks to florissmit10 for contributing PR #26731!
  • An HTTP 200 stream that ends without a grpc-status trailer now reports Unknown instead of looking like normal stream completion. This affects handling of truncated responses, including proxy or load-balancer resets.
    Thanks to pront for contributing PR #27044!
  • The elasticsearch and opensearch sinks now accept data-stream components without their own literal prefix when the complete data-stream name supplies a confinement boundary. For example, type: logs, dataset: system, and namespace: "{{ service }}" use logs-system- as the boundary, including for auto-routed destinations. Existing component prefix restrictions and routing behavior for previously supported configurations are preserved.
    Thanks to pront for contributing PR #27166!
  • AWS components now preserve request-body size hints, end-of-stream state, and trailers. This avoids unnecessary HTTP/1.1 chunked encoding for known-length bodies without an explicit Content-Length header and removes redundant empty HTTP/2 DATA frames, saving nine bytes per affected HTTP/2 request.
    Thanks to thomasqueirozb for contributing PR #27093!
  • Reduced CPU usage of metric batching in the aws_cloudwatch_metrics, sematext_metrics and influxdb_metrics sinks. Since 0.50.0, these sinks did LRU cache bookkeeping on every metric, but they never evicted metrics from the cache.
    Thanks to thomasqueirozb for contributing PR #27128!
  • The aws_cloudwatch_logs sink skips the log-group healthcheck for templated group_name values, avoiding invalid CloudWatch requests during startup and vector validate.
    Thanks to iandelahorne for contributing PR #25128!
  • AWS components now send the configured proxy credentials to an HTTP forward proxy for plain http:// AWS endpoints, for example a custom endpoint or the EC2 instance metadata service. Before, these requests reached the proxy without a Proxy-Authorization header. HTTPS requests through a CONNECT proxy are unchanged.
    Thanks to thomasqueirozb for contributing PR #26998!
  • Fixed a delay in sinks that batch events up to batch.max_bytes. When an event did not fit in the current batch and filled the next batch by itself, that next batch was sent only after batch.timeout_secs if no more events arrived. The batch is now sent immediately.

    This affects the appsignal, aws_kinesis_firehose, aws_kinesis_streams, azure_logs_ingestion, databend, databricks_zerobus, elasticsearch, gcp_stackdriver_logs, gcp_stackdriver_metrics, greptimedb_metrics, honeycomb, keep, new_relic, postgres, redis, statsd, and vector sinks.

    Thanks to thomasqueirozb for contributing PR #26958!
  • The http_client and prometheus_scrape sources now apply the configured timeout to the whole request, including reading the response body. Before, the timeout only covered sending the request and receiving the response headers, so an endpoint that sent headers and then stalled the body kept the request open indefinitely. Such requests now fail with a timeout error.
    Thanks to JinchengCao for contributing PR #27139!
  • The clickhouse, gcp_stackdriver_logs, gcp_stackdriver_metrics, greptimedb_logs, honeycomb, and keep sinks again send Accept-Encoding: zstd,gzip,deflate,br with their event requests and decompress compressed responses. Healthcheck requests are unchanged and still send Accept-Encoding: identity.

    Accept-Encoding sent with event requests:

    0.58.0 and earlier0.59.0 until this releaseThis release
    zstd,gzip,deflate,bridentityzstd,gzip,deflate,br

    Response-body transport failures remain retriable for both compressed and uncompressed responses. Malformed compressed responses are not retried.

    Thanks to thomasqueirozb for contributing PR #27094!
  • The influxdb_metrics sink now reports the result of each write to end-to-end acknowledgements. Before, metrics were acknowledged as delivered even when InfluxDB rejected the write or all retries failed, so sources with acknowledgements enabled could drop metrics that InfluxDB never stored. Rejected writes now mark their events as rejected, and writes that fail after retries mark them as errored.
    Thanks to thomasqueirozb for contributing PR #26952!
  • The prometheus_exporter sink now sends Content-Length on uncompressed responses instead of Transfer-Encoding: chunked. It also sends Vary: Accept-Encoding on responses that can be compressed, and it compresses responses for clients that send Accept-Encoding: x-gzip. Status codes and response bodies are unchanged.
    Thanks to thomasqueirozb for contributing PR #27034!
  • The webhdfs sink now retries temporary write failures instead of immediately dropping the affected batch. You can configure retry behavior and other outbound request settings through the request options.
    Thanks to zaugust4891 for contributing PR #27159!
  • The websocket source and websocket sink now fail the handshake when the server returns a Sec-WebSocket-Protocol header, because these components do not request a subprotocol (RFC 6455). Before, the header was ignored. The websocket_server sink now rejects clients that send a Sec-WebSocket-Key that is not a base64-encoded 16-byte value.
    Thanks to thomasqueirozb for contributing PR #27028!

VRL Changelog

0.39.0 (2026-11-16)

New Features

    • Added a new log10 function that computes the base 10 logarithm of a number, for example to convert milliwatts to dBm with 10 * log10!(mw).
    Thanks to lchabert for contributing PR #2012!
    • Added a new pow function that raises a number to a power, for example to convert dBm to milliwatts with pow!(10, dbm / 10).
    Thanks to lchabert for contributing PR #2012!

Fixes

    • VRL now rejects field paths with array indices outside the isize range instead of silently wrapping to a different index.
    Thanks to pront for contributing PR #2045!

Upgrade guide

  • Absent histogram sums are no longer reported as zero

    Summary

    A histogram’s sum is now optional, so a source that reports no sum no longer has one fabricated as zero. OTLP makes sum optional and OpenMetrics only recommends the _sum series, so the opentelemetry and prometheus_* sources can produce histograms without one. Downstream the sum is omitted rather than reported as zero: the prometheus_exporter and prometheus_remote_write sinks skip the <name>_sum series, influxdb_metrics omits the sum field, greptimedb_metrics omits the sum column, and a lua transform sees aggregated_histogram.sum as nil.

    Migration

    A lua transform that reads aggregated_histogram.sum must tolerate nil. Unguarded arithmetic raises attempt to perform arithmetic on a nil value, and Vector drops the event. To preserve the old behavior, default an absent sum to zero before using it in the calculation.

    Old
    transforms:
      histogram_mean:
        type: lua
        inputs: [in]
        version: "2"
        hooks:
          process: |
            function (event, emit)
              local h = event.metric.aggregated_histogram
              event.metric.gauge = { value = h.sum / h.count }
              event.metric.aggregated_histogram = nil
              emit(event)
            end
    
    New
    transforms:
      histogram_mean:
        type: lua
        inputs: [in]
        version: "2"
        hooks:
          process: |
            function (event, emit)
              local h = event.metric.aggregated_histogram
              local sum = h.sum or 0
              event.metric.gauge = { value = sum / h.count }
              event.metric.aggregated_histogram = nil
              emit(event)
            end
    

    A VRL program running after metric_to_log is affected in a narrower way. aggregated_histogram.sum could already be absent, because the whole aggregated_histogram object is absent for other metric types, so such programs already had to handle the fallible case. What is new is that the field can be absent while the object is present, so error handling that previously never triggered now can. With drop_on_error = true those events are dropped, so prefer a default:

    sum = float(.aggregated_histogram.sum) ?? 0.0
    

    Consumers of the prometheus_exporter and prometheus_remote_write sinks may see a <name>_sum series disappear for these histograms. Omitting it is valid under OpenMetrics, which forbids the series outright for histograms with negative bucket thresholds. Queries deriving an average from <name>_sum should tolerate its absence; histogram_quantile never reads it and is unaffected.

    Vector instances exchanging events with the native_json codec must run 0.60.0 or later on the receiving side before senders upgrade: older versions reject a histogram whose sum is omitted. The native protobuf codec, the vector source and sink, and disk buffers are unaffected, since older versions read a missing sum there as zero.

  • internal_metrics_cardinality_total counter removed

    Summary

    The internal_metrics source no longer emits the internal_metrics_cardinality_total counter. It was deprecated in 0.24.0 in favor of the internal_metrics_cardinality gauge, which reports the same value: the current number of metrics in the registry.

    Migration

    Update dashboards and alerts that reference internal_metrics_cardinality_total to use internal_metrics_cardinality.

  • Legacy buffer maximum-size metrics removed

    Summary

    The deprecated buffer_max_byte_size, buffer_max_event_size, source_buffer_max_byte_size, source_buffer_max_event_size, transform_buffer_max_byte_size, and transform_buffer_max_event_size gauge metrics have been removed. They were deprecated in 0.53.0 in favor of the *_max_size_bytes and *_max_size_events gauges, which report the same values.

    Migration

    Update dashboards and alerts to use the new names:

    • buffer_max_byte_size → buffer_max_size_bytes
    • buffer_max_event_size → buffer_max_size_events
    • source_buffer_max_byte_size → source_buffer_max_size_bytes
    • source_buffer_max_event_size → source_buffer_max_size_events
    • transform_buffer_max_byte_size → transform_buffer_max_size_bytes
    • transform_buffer_max_event_size → transform_buffer_max_size_events
  • Legacy process_runtime counter removed

    Summary

    The host_metrics source no longer emits the process_runtime counter. It was deprecated in 0.59.0 in favor of process_runtime_total, which reports the same value with the same tags.

    Migration

    Update dashboards and alerts that reference process_runtime to use process_runtime_total.

  • The mongodb_metrics source requires MongoDB 4.4 or newer

    Summary

    The mongodb driver is updated to 3.9.1, which removes support for MongoDB 4.2. The mongodb_metrics source now requires MongoDB server 4.4 or newer (wire version 9 or newer). Connections to MongoDB 4.2 or older servers now fail with an incompatible server error. MongoDB 4.2 reached end of life on April 30, 2023.

    Migration

    Upgrade the monitored MongoDB servers to version 4.4 or newer before you upgrade Vector.

  • Configuration is parsed before interpolation

    Summary

    Vector now parses configuration files before substituting environment variables and SECRET[backend.key] references. Substitution applies only to string values, followed by conversion to the field’s declared type. Quotes, newlines, and other configuration syntax in substituted values cannot add keys, components, or array elements.

    This removes structural interpolation, deprecated in 0.57.0. Environment-variable interpolation remains disabled by default and still requires --dangerously-allow-env-var-interpolation or VECTOR_DANGEROUSLY_ALLOW_ENV_VAR_INTERPOLATION=true.

    Migration

    Configuration must be valid YAML, TOML, or JSON before substitution. Quote placeholders in TOML and JSON values, including numeric and boolean fields. For example, change count = ${MY_COUNT} to count = "${MY_COUNT}". The same applies to secret references.

    In YAML flow collections (lists written with [...] and maps written with {...}), quote placeholders too. For example, change inputs: [${SOURCE}] to inputs: ["${SOURCE}"]. This also applies to SECRET[...] references.

    YAML string placeholders remain supported, including in numeric fields:

    sources:
      demo:
        type: demo_logs
        format: json
        count: "${MY_COUNT}"
    

    Replace interpolated map keys, component names, and table headers with literal names. Placeholders in keys and comments are no longer substituted or collected as secrets. Values cannot expand into configuration fragments or multiple array elements. For example, replace a comma-separated ${VECTOR_INPUTS} expansion with an explicit list:

    inputs:
      - "${FIRST_INPUT}"
      - "${SECOND_INPUT}"
    

    Environment-variable and secret values are now inserted as literal strings. Remove escaping that was needed only for the outer configuration format. Multiline environment values are supported within a string field, but cannot inject configuration blocks. Escaping required by an embedded language, such as VRL, is still your responsibility.

    For configurations that rely on structural environment-variable expansion, preprocess the file with a tool such as envsubst, inspect the resulting configuration, and pass that static file to Vector. envsubst does not resolve SECRET[...] references or Vector’s extended default/required-variable syntax.

Download Version 0.62.0

macOS
tar.gz
Windows
zip
Windows (MSI)
msi

Deprecation Announcements

See the deprecations page for all active and historical deprecations.

  • 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"
    
  • 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.

  • 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.
  • 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.
  • 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.

  • 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.