Vector v0.62.0 release notes
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 zeroA histogram’s sum is now optional, so a source that reports no sum no longer has one fabricated as zero. OTLP makes
sumoptional and OpenMetrics only recommends the_sumseries, so theopentelemetryandprometheus_*sources can produce histograms without one. Downstream the sum is omitted rather than reported as zero: theprometheus_exporterandprometheus_remote_writesinks skip the<name>_sumseries,influxdb_metricsomits thesumfield,greptimedb_metricsomits thesumcolumn, and aluatransform seesaggregated_histogram.sumasnil.Thanks to gwenaskell for contributing PR #25752! internal_metrics_cardinality_totalcounter removedTheinternal_metricssource no longer emits theinternal_metrics_cardinality_totalcounter. It was deprecated in 0.24.0 in favor of theinternal_metrics_cardinalitygauge, 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 removedThe deprecated
buffer_max_byte_size,buffer_max_event_size,source_buffer_max_byte_size,source_buffer_max_event_size,transform_buffer_max_byte_size, andtransform_buffer_max_event_sizegauge metrics have been removed. They were deprecated in 0.53.0 in favor of the*_max_size_bytesand*_max_size_eventsgauges, which report the same values.Thanks to JinchengCao for contributing PR #27076! - Legacy
process_runtimecounter removedThehost_metricssource no longer emits theprocess_runtimecounter. It was deprecated in 0.59.0 in favor ofprocess_runtime_total, which reports the same value with the same tags.Thanks to JinchengCao for contributing PR #27073! - The
mongodb_metricssource requires MongoDB 4.4 or newerThemongodbdriver is updated to 3.9.1, which removes support for MongoDB 4.2. Themongodb_metricssource 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-interpolationorVECTOR_DANGEROUSLY_ALLOW_ENV_VAR_INTERPOLATION=true.
3 new features
- Added a
GetCapabilitiesRPC to the Vector observability gRPC API. Clients such asvector topcan 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_agentsource now acceptsapm_stats(alpha) inenabled_data_types, which emits the APM stats sent by the Datadog Agent unmodified on a newapm_statsoutput instead of dropping them. It requiresmultiple_outputsand is not enabled whenenabled_data_typesis omitted.Thanks to antoninferrand for contributing PR #26940! Added MessagePack decoder codec
message_pack.Stream-based
socketsources (tcpandunix_streammodes) require an explicitframingmethod when usingmessage_pack.
8 enhancements
- The
aggregatetransform now supports anevent_time.late_eventsoption to control metrics that arrive after their bucket’s cutoff. Settingstrategytoforwardsends them downstream unchanged instead of dropping them, and the optionalmetric_typeslist restricts forwarding to incremental metrics of the listed types (for exampledistributionandsketch). 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_metrictransform when usingall_metrics: true.Thanks to tchanturia for contributing PR #27103! - The
datadog_agentsource now supports anenabled_data_typesoption that lists the data types (logs,metrics,traces,llmobs) the source accepts. This replaces the (now deprecated)disable_logs,disable_metrics,disable_traces, anddisable_llmobsoptions. Please see the dedicated migration notice.Thanks to antoninferrand for contributing PR #27000! - The
datadog_tracessink now supports adisable_apm_statsoption, 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 withinvalid 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_metricsandaws_ecs_metricssources, and to theendpointandtagsoptions of theaws_ec2_metadatatransform. Thehttp_clientandprometheus_scrapesources percent-encode the query string before they send the request.This does not apply to the
httpsink’suri, theopentelemetrysink’sprotocol.uri, or theaxiomsink’surl. 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.- The
internal_metricssource has a newemit_incrementaloption that emits counters and histograms as increments since the previous scrape instead of absolute totals. This keeps sinks likedatadog_metricsfrom 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
remaptransform can now change a metric’s type betweencounterandgaugeby 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.
23 bug fixes
Fixed mutual TLS (mTLS) authentication by properly passing client certificates in the
amqpsource and sink.A configuration that specifies both
tls.crt_fileand a PKCS#12 archive intls.key_filenow fails, because that setup contradicts the documented TLS configuration. For more information, see theamqpsource docs andamqpsink docs.Thanks to Captain1653 for contributing PR #27130!- Fixed an issue in the
amqpsink where configuring a DER or inline PEM certificate intls.ca_filecaused initialization errors.Thanks to Captain1653 for contributing PR #27100! - The
http_clientsource now sendsAccept: application/jsonwhendecoding.codecisjson,native_jsonorgelfand the defaultbytesframing is used. Previously it sentAccept: text/plain. - Messages that are not valid UTF-8 no longer fail
octet_counting, the framing thesyslogsource uses, in either its octet-counted or newline-delimited mode. UTF-8 handling is now done by the configured deserializer.syslogdecoding replaces invalid sequences with U+FFFD by default (lossy). Because framing no longer errors, thesyslogsource 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_metrictransform withall_metrics: truenow accepts integer values wherever it expects a float (for examplecounter.value,gauge.value, histogramupper_limitandsum, summaryquantile,valueandsum). Previously a value such as42was rejected with a “Failed to parse field as float” error and the event was dropped, while42.0worked. vector tapnow exits cleanly when its output pipe is closed, for examplevector tap | head -1, instead of panicking with “failed printing to stdout: Broken pipe”.- Fixed
sum/avgreported by the DDSketch generated when converting anAggregatedHistogram(used by thedatadog_metricssink, 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/avgare 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+Infbucket — or if that exact sum is not a finite number). - The sketch conversion used by the
datadog_metricssink 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
remaptransform’s “Event mapping aborted.” debug log now includes the message given toabortin itserrorfield, so the reason for a dropped event is no longer lost whenreroute_droppedis not enabled. - The
mqttsource 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-statustrailer now reportsUnknowninstead of looking like normal stream completion. This affects handling of truncated responses, including proxy or load-balancer resets. - The
elasticsearchandopensearchsinks 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, andnamespace: "{{ service }}"uselogs-system-as the boundary, including for auto-routed destinations. Existing component prefix restrictions and routing behavior for previously supported configurations are preserved. - 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-Lengthheader 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_metricsandinfluxdb_metricssinks. 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_logssink skips the log-group healthcheck for templatedgroup_namevalues, avoiding invalid CloudWatch requests during startup andvector 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 customendpointor the EC2 instance metadata service. Before, these requests reached the proxy without aProxy-Authorizationheader. HTTPS requests through aCONNECTproxy 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 afterbatch.timeout_secsif 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, andvectorsinks.Thanks to thomasqueirozb for contributing PR #26958!- The
http_clientandprometheus_scrapesources 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, andkeepsinks again sendAccept-Encoding: zstd,gzip,deflate,brwith their event requests and decompress compressed responses. Healthcheck requests are unchanged and still sendAccept-Encoding: identity.Accept-Encodingsent with event requests:0.58.0 and earlier 0.59.0 until this release This release zstd,gzip,deflate,bridentityzstd,gzip,deflate,brResponse-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_metricssink 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_exportersink now sendsContent-Lengthon uncompressed responses instead ofTransfer-Encoding: chunked. It also sendsVary: Accept-Encodingon responses that can be compressed, and it compresses responses for clients that sendAccept-Encoding: x-gzip. Status codes and response bodies are unchanged.Thanks to thomasqueirozb for contributing PR #27034! - The
webhdfssink now retries temporary write failures instead of immediately dropping the affected batch. You can configure retry behavior and other outbound request settings through therequestoptions.Thanks to zaugust4891 for contributing PR #27159! - The
websocketsource andwebsocketsink now fail the handshake when the server returns aSec-WebSocket-Protocolheader, because these components do not request a subprotocol (RFC 6455). Before, the header was ignored. Thewebsocket_serversink now rejects clients that send aSec-WebSocket-Keythat 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
log10function that computes the base 10 logarithm of a number, for example to convert milliwatts to dBm with10 * log10!(mw).
- Added a new
- Added a new
powfunction that raises a number to a power, for example to convert dBm to milliwatts withpow!(10, dbm / 10).
- Added a new
Fixes
- VRL now rejects field paths with array indices outside the
isizerange instead of silently wrapping to a different index.
- VRL now rejects field paths with array indices outside the
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
sumoptional and OpenMetrics only recommends the_sumseries, so theopentelemetryandprometheus_*sources can produce histograms without one. Downstream the sum is omitted rather than reported as zero: theprometheus_exporterandprometheus_remote_writesinks skip the<name>_sumseries,influxdb_metricsomits thesumfield,greptimedb_metricsomits thesumcolumn, and aluatransform seesaggregated_histogram.sumasnil.Migration
A
luatransform that readsaggregated_histogram.summust toleratenil. Unguarded arithmetic raisesattempt 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) endNew
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) endA VRL program running after
metric_to_logis affected in a narrower way.aggregated_histogram.sumcould already be absent, because the wholeaggregated_histogramobject 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. Withdrop_on_error = truethose events are dropped, so prefer a default:sum = float(.aggregated_histogram.sum) ?? 0.0Consumers of the
prometheus_exporterandprometheus_remote_writesinks may see a<name>_sumseries 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>_sumshould tolerate its absence;histogram_quantilenever reads it and is unaffected.Vector instances exchanging events with the
native_jsoncodec must run 0.60.0 or later on the receiving side before senders upgrade: older versions reject a histogram whosesumis omitted. Thenativeprotobuf codec, thevectorsource and sink, and disk buffers are unaffected, since older versions read a missing sum there as zero.internal_metrics_cardinality_totalcounter removedSummary
The
internal_metricssource no longer emits theinternal_metrics_cardinality_totalcounter. It was deprecated in 0.24.0 in favor of theinternal_metrics_cardinalitygauge, which reports the same value: the current number of metrics in the registry.Migration
Update dashboards and alerts that reference
internal_metrics_cardinality_totalto useinternal_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, andtransform_buffer_max_event_sizegauge metrics have been removed. They were deprecated in 0.53.0 in favor of the*_max_size_bytesand*_max_size_eventsgauges, which report the same values.Migration
Update dashboards and alerts to use the new names:
buffer_max_byte_size→buffer_max_size_bytesbuffer_max_event_size→buffer_max_size_eventssource_buffer_max_byte_size→source_buffer_max_size_bytessource_buffer_max_event_size→source_buffer_max_size_eventstransform_buffer_max_byte_size→transform_buffer_max_size_bytestransform_buffer_max_event_size→transform_buffer_max_size_events
Legacy
process_runtimecounter removedSummary
The
host_metricssource no longer emits theprocess_runtimecounter. It was deprecated in 0.59.0 in favor ofprocess_runtime_total, which reports the same value with the same tags.Migration
Update dashboards and alerts that reference
process_runtimeto useprocess_runtime_total.The
mongodb_metricssource requires MongoDB 4.4 or newerSummary
The
mongodbdriver is updated to 3.9.1, which removes support for MongoDB 4.2. Themongodb_metricssource 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-interpolationorVECTOR_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}tocount = "${MY_COUNT}". The same applies to secret references.In YAML flow collections (lists written with
[...]and maps written with{...}), quote placeholders too. For example, changeinputs: [${SOURCE}]toinputs: ["${SOURCE}"]. This also applies toSECRET[...]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.envsubstdoes not resolveSECRET[...]references or Vector’s extended default/required-variable syntax.
Deprecation Announcements
See the deprecations page for all active and historical deprecations.
- 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" 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.- 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.
- 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
- 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.- 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.