The Vector team is pleased to announce version 0.34.0!
Be sure to check out the upgrade guide for breaking changes in this release.
In addition to the usual enhancements and bug fixes, this release also includes
protobufencoder for sinks.
This release also marks the deprecation of the OS package repositories hosted at
repositories.timber.io. Instead, packages have been moved to
yum.vector.dev. Please see the release
highlight for details about this change and
instructions on how to migrate. The repositories located at
be decommissioned on February 28th, 2024.
Content-Encodingheader on requests to
application/jsonwhen the default
snappycompression is used. This results in Loki rejecting the requests with an HTTP 400 response. This is fixed in v0.34.1.
protobufencoder does not work in sinks #19230.
Sinks now have additional options for
unix_float: Represents the timestamp as a Unix timestamp in floating point.
unix_ms: Represents the timestamp as a Unix timestamp in milliseconds.
unix_ns: Represents the timestamp as a Unix timestamp in nanoseconds.
unix_us: Represents the timestamp as a Unix timestamp in microseconds
prometheus_remote_writesink now has the ability to disable aggregation by setting
natssource has a new
subscriber_capacityconfiguration option to control how many messages the NATS subscriber buffers before incoming messages are dropped.
Sources and sinks that run a HTTP server now emit additional internal metrics:
Sources that run a gRPC server now emit additional internal metrics:
Event metadata, including secrets like Datadog API key or Splunk HEC token, are now persisted when writing events to a disk buffer so that sinks have access to it.
As part of this change, disk buffers created by Vector now have more restrictive
file permissions on Unix platforms. Previously, they were world-readable, but are now
only writable by the Vector process user (typically
vector) and readable by group.
See the release highlight for details about this change and recommended practices to either secure the disk buffers or to avoid storing secrets in events altogether.
journaldsource has a new
emit_cursoroption that, when enabled, adds the
__CURSORfield to emitted log records. Thanks to sproberts92 for contributing this change!
protobufencoder (configurable using
encoding.codec). Thanks to goakley for contributing this change!
Vector’s version of VRL was updated to 0.8.1, with the following changes:
from_unix_timestampnow accepts a new unit,
parse_nginx_logno longer fails if
--allow-empty-config. This is useful if you want to start Vector before loading a configuration using
--watch-configor when reloading.
docker_logssource no longer increments
component_errors_totalfor out-of-order logs since this is not an error.
native_jsoncodec no longer errors when encoding 64-bit float values that represent infinity. Instead, these are encoded as the strings
-inf. This most commonly occurred when encoding histograms where the last bucket bound included infinity.
http_serversource no longer panics when handling metrics decoded using the
native_jsoncodecs. This means that it can now be used in conjunction with the
httpsink to send data between Vector instances using the
native_jsoncodecs; however, the
vectorsource/sink pair is still the preferred route for Vector-to-Vector communication.
kafkasource now fully drains acknowledgements during consumer group rebalancing and when Vector is shutting down. This avoids situations where Vector would duplicate message processing. Thanks to jches for contributing this change!
gcp_stackdriver_metricssink now correctly handles configured batch sizes greater than the default of
1. Previously it would only send the last event in each batch.
tls.alpn_protocolsoptions. Previously, these were only applied for sources creating outgoing TLS connections. Thanks to anil-db for contributing this change!
component_discarded_events_totalwhen incoming requests are cancelled before the events are pushed to downstream components.
amqpsink no longer panics when the channel is in an error state. Instead, Vector now emits an error event when this occurs.
datadog_agentsource now records the “interval” on any incoming metrics that have it set rather than just
rate. This is useful as metrics can be interpreted as rates later when viewing the data in Datadog, where the
intervalfield will be used.
blackhole sink no longer reports events processed by default. Instead, this
behavior can be opted into by setting
print_interval_secs to a non-zero number.
See the upgrade guide for more details.
clickhousesink heath check where it would add an extra
/to the URI, resulting in failures, was fixed. This was a regression in v0.33.0.
Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter