Vector v0.36.0 release notes
- AWS components don’t support use of
credentials_processin AWS configs. Fixed in v0.36.1. - AWS components don’t support auto-detection of region . Fixed in v0.36.1.
- AWS components don’t support use of
assume_role. Fixed in v0.36.1. - The
kafkasink occasionally panics during rebalance events. Fixed in v0.36.1.
The Vector team is pleased to announce version 0.36.0!
There are no breaking changes in this release.
In addition to the usual enhancements and bug fixes, this release also includes
- A new
prometheus_pushgatewaysource to receive Prometheus data - A new
vrldecoder that can be used to decode data in sources using a VRL program
A reminder that the repositories.timber.io package repositories will be decommissioned on
February 28th, 2024. Please see the release
highlight for details about this change and
instructions on how to migrate.
Vector Changelog
4 new features
Vector can now emulate a Prometheus Pushgateway through the new
prometheus_pushgatewaysource. Counters and histograms can optionally be aggregated across pushes to support use-cases like cron jobs.There are some caveats, which are listed in the implementation.
Thanks to Sinjo for contributing this change!- The
clickhousesink now supportsformat. This can be used to specify the data format provided toINSERTs. The default isJSONEachRow.
Thanks to gabriel376 for contributing this change! - Added a configuration option for the
aws_s3source that prevents deletion of messages which failed to be delivered to a sink.
Thanks to tanushri-sundar for contributing this change! - Implemented VRL decoder. This enables users to set
decoding.codec = "vrl"in their source configurations and use VRL programs to decode logs.
6 enhancements
- Unit tests can now populate event metadata with the
% = ...syntax.
Thanks to GreyTeardrop for contributing this change! - Added support for parsing HTTPS (type 65) and SVCB (type 64) resource records from DNS messages
Thanks to esensar, Quad9DNS for contributing this change! - The base for Vector’s Alpine Docker images was updated from 3.18 to 3.19.
- Gracefully accept
@characters in labels when decoding GELF.
Thanks to MartinEmrich for contributing this change! Added a boolean
graphqlfield to the api configuration to allow disabling the graphql endpoint.Note that the
playgroundendpoint will now only be enabled if thegraphqlendpoint is also enabled.New Option
--skip-healthchecksforvector validatevalidates config including VRL, but skips health checks for sinks.Useful to validate configuration before deploying it remotely.
Thanks to MartinEmrich for contributing this change!
6 bug fixes
- Fixed an issue where the
aws_s3sink adds a trailing period to the s3 key when thefilename_extensionis empty. - Removed warnings for unused outputs in
datadog_agentsource when the corresponding output is disabled in the source config. - When terminating idle HTTP connections using the configured
max_connection_age, only sendConnection: Closefor HTTP/0.9, HTTP/1.0, and HTTP/1.1 requests. This header is not supported on HTTP/2 and HTTP/3 requests. This may be supported on these HTTP versions in the future. The following metrics now correctly have the
component_kind,component_type, andcomponent_idtags: -component_errors_total-component_discarded_events_totalFor the following sinks: -
splunk_hec-clickhouse-loki-redis-azure_blob-azure_monitor_logs-webhdfs-appsignal-amqp-aws_kinesis-statsd-honeycomb-gcp_stackdriver_metrics-gcs_chronicle_unstructured-gcp_stackdriver_logs-gcp_pubsub-gcp_cloud_storage-nats-http-kafka-new_relic-datadog_metrics-datadog_traces-datadog_events-databend-prometheus_remote_write-pulsar-aws_s3-aws_sqs-aws_sns-elasticsearch- Fixed an issue where the
journaldsource was not correctly emitting metadata whenlog_namespace = True.
Thanks to dalegaard for contributing this change! - Fixed an issue where the
datadog_logssink could produce a request larger than the allowed API limit.