The Vector team is pleased to announce version 0.18.0!
Be sure to check out the upgrade guide for breaking changes in this release.
In case you missed it, we’ve also released a new unified
vector helm chart! This new chart can deployed as either
as either an agent or aggregator role and so deprecates our existing
See the chart upgrade
guide for how to
transition from the old charts.
elasticsearchsink incorrectly prints a message for each delivered event. Fixed in v0.18.1.
prometheus_remote_writesinks to be incorrectly tallied. Fixed in v0.18.1.
/etc/vectorthat are not valid. Fixed in v0.18.1.
remapalways creates the
droppedoutput even if
reroute_dropped = false. Fixed in v0.18.1.
headers_keyoption for the
kafkasink was inadvertantly changed to
headers_field. Fixed in v0.19.0.
--config-diris used, Vector incorrectly tries to load files with unknown extensions. Fixed in v0.19.0.
encoding.only_fields failed to deserialize correctly for sinks that used fixed encodings (i.e. those that don’t have
encoding.codec). Fixed in v0.19.2. As a workaround, you can split the paths up in your configuration like:
encoding.only_fields = ["message", "foo.bar"]
encoding.only_fields = [["message"], ["foo", "bar"]]
You will need to convert it back to its original representation when upgrading to >= v0.19.2.
batch.max_sizeparameter has been removed in this release. See the upgrade guide for more.
request.in_flight_limithas been removed in this release. See the upgrade guide for more.
namespacefield on the
datadog_metricssink has been removed. See the upgrade guide for more.
Instrumentation has been added to sink buffers to help give more visibility into their operation. The following metrics have been added:
buffer_byte_size(disk buffer only): The number of bytes in the buffer
buffer_events(in-memory buffer only): The number of events in the buffer
buffer_received_event_bytes_total: The number of bytes that have been received by this buffer. This count does not include discarded events.
buffer_sent_event_bytes_total: The number of bytes that have been sent from the buffer to its associated sink.
buffer_received_events_total: The number of events that have been received by this buffer. This count does not include discarded events.
buffer_sent_events_total: The number of events that have been sent from the buffer to its associated sink.
buffer_discarded_events_total: The number of events that have been discarded from the buffer because it is full (relevant when
$LOGenvironment variable for configuring the Vector log level has been renamed to
$LOGis still also accepted for backwards compatibility. This change makes logging configuration more in-line with Vector’s other environment variable based options, and isolates Vector from being affected by other generic environment variables.
falsefor undefined variables. This helps guide users to realize when they are trying to use a keyword like
nilthat doesn’t actually exist in VRL.
log_to_metrictransform now also allows emitting absolute counters in addition to relative counters via
kind = "absolute".
statustag for the
http_client_responses_totalinternal metric was updated to be just the integer (e.g.
200) rather than including the text portion of the HTTP response code (e.g.
kubernetes_logssource now annotates logs with the
papertrailsink now allows
processfield to be set to a event field value the templatable
aws_s3sink now has less connections terminated prematurely as it optimistically terminates connections before AWS’s timeout.
prometheus_exporternow expires metrics that haven’t been seen since the last flush (controlled by
flush_interval_secs) to avoid holding onto stale metrics indefinitely and consuming increasing amounts of memory.
utilizationmetric for most transforms no longer count time spent blocked on downstream components as busy. This means they should more accurately represent the time spent in that specific transform and require less interpretation to find bottlenecks.
datadog_metricssink now supports sending distribution data to Datadog like histograms and aggregated samples.
kubernetes_logssource has been updated to be less demanding on the Kubernetes API server (and backing etcd cluster) by allowing for slightly stale data to be used for log enrichment rather than always requesting the most-up-to-date metadata.
generatorsource has been renamed to
demo_logs. We feel this name better reflects the intent of the source. An alias has been added to maintain compatibility.
decodingoptions are now available on
heroku_logssource. See the framing and decoding highlight from v0.17.0 for more about this new source feature.
upper_limitfield for aggregated summaries from the
metric_to_logtransform has been renamed to
qwhich is a common shorthand for
remaptransform. See the highlight for more.
throttletransform has been added for controlling costs. See the highlight for more.
aws_sqssource was added for consuming messages from AWS SQS as log events.
--threads) for Vector now actually takes effect again rather than it always using the number of available cores. This was a regression in v0.13.
event_per_lineconfiguration option was removed from the
execsource. This option became non-functional in 0.17.0 but was left available to be configured. Instead, the new
framingoption can be used to choose between interpreting th e output of the subcommand as an event per line or all at once as one event.
aws_s3sink where it would add a
/to the prefix provided. The sink no longer adds this
/to replace previous behavior.
objectargument to match the docs. This was incorrectly implemented named
mapin the implementation.
component_sent_bytes_totalinternal metric is now reported after events are successfully sent to HTTP-based sinks rather than before they are sent.
influxdb_logssinks now use
/pingfor heathchecks rather than
/healthto work with Influx DB 2 Cloud.
Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter