The Vector team is pleased to announce version 0.28.0!
This is a smaller maintenance release primarily including bug fixes and small enhancements, while we do some background work to enable upcoming new features.
With this release we also completed an initiative to generate Vector’s reference documentation from the configuration structures in the code which will result in less inaccuracies in published documentation.
Be sure to check out the upgrade guide for breaking changes in this release.
aws_s3sink, are not functional due to issues with request signing. This is fixed in v0.28.1.
framing.*.max_lengthconfiguration options cannot be used on the
socketsource as Vector returns an error about them conflicting with the deprecated top-level
max_lengthconfiguration option. This is fixed in v0.28.1.
http_serversource incorrectly defaults to
method. Fixed in 0.28.2.
elasticsearchsink panics when starting if
bulk.indexis unspecified and the default
bulkis used. Fixed in 0.28.2.
syslogsource incorrectly inserted the source IP of incoming messages as
source_ip. Fixed in 0.28.2.
azure_blobsink now allows setting a custom
endpointfor use with alternative Azure clouds like USGov and China. Thanks to archoversight for contributing this change!
clickhousesink now supports a
date_time_best_effortconfig option to have ClickHouse parse a greater variety of timestamps (like RFC3339). Thanks to DarkWanderer for contributing this change!
httpsink now supports
payload_suffixoptions to prepend and append text in the HTTP bodies it is sending. This happens after batches are encoded and so can be used, for example, to wrap the batches in a JSON envelope. Thanks to jdiebold for contributing this change!
aws_kinesis_firehosenow has a
store_access_key, similar to the
datadog_agentsources, to store the token that the incoming request was sent with in the event secrets. This can be read later in VRL to drive behavior. Thanks to dizlv for contributing this change!
reducetransform now has a
max_eventsoption that can be used to limit the total number of events in a reduced batch. Thanks to jches for contributing this change!
kafkasource now tries to commit offsets during shutdown to avoid duplicate processing on start-up. Thanks to aholmberg for contributing this change!
reducetransform performance improved by only flushing when events were ready to be flushed and avoiding repeated checks for stale events. Thanks to dbcfd for contributing this change!
seahashfunction was added to VRL for a non-cryptographic fast hash. Thanks to psemeniuk for contributing this change!
pulsarsink now supports batching via the added
batch.max_eventsconfiguration option. Thanks to zamazan4ik for contributing this change!
kafkasource is now capable of making consumer lag metrics available via the
internal_metricssource. This can be enabled by setting
true. Note that this can result in high cardinality metrics given they are tagged with the topic and partition id. Thanks to zamazan4ik for contributing this change!
redissource now retries failed requests with an exponential back-off rather than immediately (which can cause high resource usage). Thanks to hargut for contributing this change!
decode_gzipfunctions were added to VRL to interact with gzip’d data. Thanks to zamazan4ik for contributing this change!
decode_zlibfunctions were added to VRL to interact with zlib compressed data. Thanks to zamazan4ik for contributing this change!
decode_zstdfunctions were added to VRL to interact with zstd compressed data. Thanks to zamazan4ik for contributing this change!
filesource no longer typically invalidates all previous checksums. It still will invalidate the checksum if the value is set to lower than the length of the line used that checksum but this should be much less common. Thanks to Ilmarii for contributing this change!
gcp_stackdriver_metricsnow correctly encodes metrics to send to GCP. Thanks to jasonahills for contributing this change!
axiomsink now always sets the
timestamp-fieldheader, which tells Axiom where to find the timestamp, to
@timestamprather than the configured
log_schema.timestamp_keysince Vector was always sending it as
@timestamp.the upgrade guide for details.
Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter