Vector releases

The Vector team is pleased to announce version 0.42.0!

This release contains a number of enhancements and fixes as listed below.

There are no breaking changes or deprecations with this release and so no upgrade guide.

The Vector team is pleased to announce version 0.41.1!

This release includes a bug fix for a regression in the vector source and native codecs where an error log was spuriously reported when receiving events from older Vector versions.

The Vector team is pleased to announce version 0.41.0!

In addition to the enhancements and fixes listed below, this release includes the following notable features:

• A new greptimedb_logs sink was added for sending logs to GreptimeDB
• A new static_metrics source was added for emitting preconfigured metrics on an interval. This can be useful for heartbeat-style metrics or for emitting a metric based on an environment variable.
• Windows now supports automatic config reloading via --watch-config as exists on other *nix platforms.

There are no breaking changes or deprecations with this release and so no upgrade guide.

The Vector team is pleased to announce version 0.40.2!

This release also fixes regression in the reduce transform in Vector v0.40.0.

The Vector team is pleased to announce version 0.40.1!

This is the first release with packages signed with the new GPG key as part of Datadog’s key rotation. This should be a transparent change for users as the package repository setup script setup.vector.dev has already been importing the new key; however, if you were manually managing the trusted GPG keys, you will need to update to the newer ones (either apt or rpm.

This release also fixes a regression in Vector v0.40.0.

The Vector team is pleased to announce version 0.40.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release contains a mix of enhancements and bug fixes. See the changelog below.

The Vector team is pleased to announce version 0.39.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release just contains a mix of small enhancements and bug fixes. See the changelog below.

The Vector team is pleased to announce version 0.38.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release just contains a mix of small enhancements and bug fixes. See the changelog below.

This patch release contains fixes for regressions in 0.37.0.

Note: Please see the release notes for v0.37.0 for additional changes if upgrading from v0.36.X. In particular, see the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.37.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

• ARMv6 builds of Vector including Debian archives and container images. The Debian archives, for now, are only hosted as release assets and are not published to the Debian repository. We are looking into publishing them there in the future. No RPM packages are built at this time. Kudos to @wtaylor for this contribution.
• A new mqtt sink to emit events from Vector using the MQTT protocol. A source is in the works. Kudos to the contributors that pushed this forward: @astro, @zamazan4ik, and @mladedav.
• The dnstap source now supports reading events over TCP. Kudos to @esensar for this contribution.
• A new mmdb enrichment table type for loading arbitrary mmdb databases and not just GeoIP ones. Kudos to @esensar for this contribution.
• A new pulsar source for receiving events from Pulsar. Kudos to @zamazan4ik and @WarmSnowy for this contribution.

This patch release contains fixes for regressions in 0.36.0.

Note: Please see the release notes for v0.36.0 for additional changes if upgrading from v0.35.X. In particular, see the upgrade guide for breaking changes.

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_pushgateway source to receive Prometheus data
• A new vrl decoder 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.

This patch release contains fixes for regressions in 0.35.0.

Note: Please see the release notes for v0.35.0 for additional changes if upgrading from v0.34.X. In particular, see the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.35.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

• The ability to use VRL to specify inputs for unit tests
• A new avro decoder that can used to decode AVRO data in sources

This release is also the first release only published to the new apt.vector.dev and yum.vector.dev OS package repositories and not to the deprecated repositories.timber.io. 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.

This patch release contains fixes for regressions in 0.34.0.

Note: Please see the release notes for v0.34.0 for additional changes if upgrading from v0.33.X. In particular, see the upgrade guide for breaking changes.

This patch release contains fixes for regressions in 0.34.0 and fixes an issues with the Debian release artifacts.

Note: Please see the release notes for v0.34.0 for additional changes if upgrading from v0.33.X. In particular, see the upgrade guide for breaking changes.

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

• A new protobuf encoder for sinks.
• A fix to pass event metadata and secrets through disk buffers to have this data available in sinks. Note this change has potential security implications as things like Datadog API keys or Splunk HEC tokens could end up persisted in disk buffers. 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.

This release also marks the deprecation of the OS package repositories hosted at repositories.timber.io. Instead, packages have been moved to apt.vector.dev and yum.vector.dev. Please see the release highlight for details about this change and instructions on how to migrate. The repositories located at repositories.timber.io will be decommissioned on February 28th, 2024.

This patch release contains fixes for regressions in 0.33.0 and fixes an issues with the Debian release artifacts.

Note: Please see the release notes for v0.33.0 for additional changes if upgrading from v0.32.X. In particular, see the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.33.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release marks the switch of the default configuration language for Vector from TOML to YAML. We continue to support both (as well as JSON), but the documentation will prefer YAML in its configuration examples. We think this will lead to more legible configurations as well as more consistency with Vector’s Helm chart which requires YAML configuration. See the associated release highlight for more details on the motivation for this change.

In addition to the usual enhancements and bug fixes, this release includes also includes:

• A new AWS SNS sink

This patch release contains a fix for a regression in 0.32.0.

Note: Please see the release notes for v0.32.0 for additional changes if upgrading from v0.31.X. In particular, the upgrade guide for breaking changes.

This patch release contains a fix for a regression in 0.32.0 and fixes a few issues with the release artifacts.

Note: Please see the release notes for v0.32.0 for additional changes if upgrading from v0.31.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.32.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 includes:

• a new greptimedb sink for sending metrics to GreptimeDB
• a new protobuf codec that can be used on sources that support codecs to decode incoming protobuf data

The Vector team is pleased to announce version 0.31.0!

Be sure to check out the upgrade guide for breaking changes in this release.

In addition to the usual smaller enhancements and bug fixes, this release includes an opt-in beta of a new log event data model that we think will make it easier to process logs by moving event metadata out of the log event itself. We are looking for feedback on this new feature before beginning towards making it the default and eventually removing the old log event data model.

By way of example, an example event from the datadog_agent source currently looks like:

{
	"ddsource": "vector",
	"ddtags": "env:prod",
	"hostname": "alpha",
	"foo": "foo field",
	"service": "cernan",
	"source_type": "datadog_agent",
	"bar": "bar field",
	"status": "warning",
	"timestamp": "1970-02-14T20:44:57.570Z"
}

Will now look like:

{
	"foo": "foo field",
	"bar": "bar field"
}

(just the event itself)

with additional buckets for source added metadata:

{
	"ddsource": "vector",
	"ddtags": "env:prod",
	"hostname": "alpha",
	"service": "cernan",
	"status": "warning",
	"timestamp": "1970-02-14T20:44:57.570Z"
}

accessible via %<datadog_agent>.<field>, and Vector added metadata:

{
	"source_type": "datadog_agent",
	"ingest_timestamp": "1970-02-14T20:44:58.236Z"
}

accessible via %vector.<field>.

We think this new organization will be easier to reason about for users as well as avoid key conflicts between event fields and metadata.

You can opt into this feature by setting schema.log_namespace as a global setting or the log_namespace option now available on each source itself. See the blog post for an expanded explanation and details. Let us know what you think on this issue.

The Vector team is pleased to announce version 0.30.0!

In addition to the usual smaller enhancements and bug fixes, this release also includes a refresh of the component statuses in the docs following the stability guarantees.

Be sure to check out the upgrade guide for breaking changes in this release.

This patch release contains a fix for a regression in 0.29.0 and fixes a few issues with the release artifacts.

Note: Please see the release notes for v0.29.0 for additional changes if upgrading from v0.28.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.29.0!

In addition to the usual smaller enhancements and bug fixes, this release also includes:

• A new appsignal sink to send logs and metrics to AppSignal
• A new databend sink to send logs to Databend
• A new webhdfs sink to send log data to HDFS via the WebHDFS interface.
• A new csv encoding option for sinks to encode events as CSV

Be sure to check out the upgrade guide for breaking changes in this release.

Special thanks to Xuanwo for collaborating with us to introduce the OpenDAL library into Vector, starting with the webhdfs sink, to prove out the ability to use it to more easily support additional Vector sinks in the future.

Additionally, for Vector developers, two new tutorials were added for developing Vector sinks: docs. We hope this makes it easier to add Vector sinks in the future.

This patch release contains a few fixes for regressions in 0.28.0 and 0.27.0.

Note: Please see the release notes for v0.28.0 for additional changes if upgrading from v0.27.X. In particular, the upgrade guide for breaking changes.

This patch release contains a few fixes for regressions in 0.28.0.

Note: Please see the release notes for v0.28.0 for additional changes if upgrading from v0.27.X. In particular, the upgrade guide for breaking changes.

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.

This patch release contains a few fixes for regressions in 0.27.1.

Note: Please see the release notes for v0.27.0 for additional changes if upgrading from v0.26.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.27.0!

This release includes the usual litany of smaller enhancements and bug fixes as well as:

• Support for a new metric tag data model that supports a wider range of tags than the simple key/value pairs previously allowed including tags that are not key/value as well as tag keys that appear multiple times, with different values. See the release highlight for more details about this feature and how to enable it.
• Support for tracing memory allocations within Vector to aid in troubleshooting Vector’s memory use. See the announcement blog post for more details about this feature and how to enable it.

Be sure to check out the upgrade guide for breaking changes in this release.

The Vector team is pleased to announce version 0.26.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This is a smaller release primarily including bug fixes and small enhancements.

This patch release contains a few fixes for regressions in 0.25.0.

Note: Please see the release notes for v0.25.0 for additional changes if upgrading from v0.24.X. In particular, the upgrade guide for breaking changes.

This patch release contains a few fixes for regressions in 0.25.0.

Note: Please see the release notes for v0.25.0 for additional changes if upgrading from v0.24.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.25.0!

Be sure to check out the upgrade guide for breaking changes in this release.

In addition to the new features, enhancements, and fixes listed below, this release adds:

• A new http_client source
• A new amqp source and sink that supports AMQP 0.9.1 (used by RabbitMQ)

This patch release contains a few fixes for regressions and bugs in new functionality from 0.24.0.

Note: Please see the release notes for v0.24.0 for additional changes if upgrading from v0.23.X. In particular, the upgrade guide for breaking changes.

This patch release contains a few fixes for regressions in 0.24.0.

Note: Please see the release notes for v0.24.0 for additional changes if upgrading from v0.23.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.24.0!

Be sure to check out the upgrade guide for breaking changes in this release.

In addition to the new features, enhancements, and fixes listed below, this release adds:

• A new axiom sink for sending events to Axiom
• A new gcp_chronicle_unstructured sink for sending unstructured log events to GCP Chronicle
• A new file_descriptor source to consume input from file descriptors
• A new opentelemetry source to receive input from OpenTelemetry collectors and SDKs. Only logs are supported in this release, but support for metrics and traces are in-flight. An opentelemetry sink will follow.
• Support for expiring high cardinality internal metrics through the global expire_metrics (will be replaced by expire_metrics_secs in 0.24.1). This can alleviate issues with Vector using increased memory over time. For now it is opt-in, but we may make this the default in the future.

Note that this release has a backwards incompatible data model change that users of the vector sink and disk buffers should be aware of while upgrading. See the note in the upgrade guide for more details.

This patch release contains a few fixes for regressions in 0.23.0.

This is the first release after 0.23.0, versions 0.23.1 and 0.23.2 were inadvertently skipped due to a version mismatch during release.

Note: Please see the release notes for v0.23.0 for additional changes if upgrading from v0.22.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.23.0!

Be sure to check out the upgrade guide for breaking changes in this release.

In addition to the new features, enhancements, and fixes listed below, this release adds:

• Support for loading secrets from an external process. See the release highlight for details.
• Support for new encoding options to all sinks that support codecs, that mirror the decoding options available on sources. This allows for more codecs (like json and logfmt) and framings (like newline-delimited and length-delimited) to be used on more sinks. See the release highlight for details.

This patch release contains a few fixes for regressions in 0.22.0.

Note: Please see the release notes for v0.22.0 for additional changes if upgrading from v0.20.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.22.2!

Note this release does include one potentially impactful behavior change to fix a bug in the internal_logs source. The internal_logs source now, as was intended, applies the same rate limiting logic applied to logs that Vector would write to stderr. This means, rather than seeing each log individually, duplicate logs in small time windows are rolled up and logged like:

{"host":"consigliere","message":"Internal log [function call error for "parse_json" at (14:34): unable to parse json: trailing characters at line 1 column 8] has been rate limited 282948 times.","metadata":{"kind":"event","level":"ERROR","module_path":"vrl_stdlib::log","target":"vrl_stdlib::log"},"pid":2064943,"source_type":"internal_logs","timestamp":"2022-06-14T22:52:50.329188616Z","vector":{"component_id":"transform0","component_kind":"transform","component_name":"transform0","component_type":"remap"}}
{"host":"consigliere","internal_log_rate_secs":1,"message":"function call error for "parse_json" at (14:34): unable to parse json: trailing characters at line 1 column 8","metadata":{"kind":"event","level":"ERROR","module_path":"vrl_stdlib::log","target":"vrl_stdlib::log"},"pid":2064943,"source_type":"internal_logs","timestamp":"2022-06-14T22:52:50.329201656Z","vector":{"component_id":"transform0","component_kind":"transform","component_name":"transform0","component_type":"remap"},"vrl_position":54}
{"host":"consigliere","message":"Internal log [function call error for "parse_json" at (14:34): unable to parse json: trailing characters at line 1 column 8] is being rate limited.","metadata":{"kind":"event","level":"ERROR","module_path":"vrl_stdlib::log","target":"vrl_stdlib::log"},"pid":2064943,"source_type":"internal_logs","timestamp":"2022-06-14T22:52:50.329212676Z","vector":{"component_id":"transform0","component_kind":"transform","component_name":"transform0","component_type":"remap"}}

This change was made to bring internal_logs in line with Vector’s logging and avoid unexpected high bills from ingestion in downstream systems when a catastrophic failure occurs.

Note: Please see the release notes for v0.22.0 for additional changes if upgrading from v0.21.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.22.1!

Note: Please see the release notes for v0.22.0 for additional changes if upgrading from v0.21.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.22.0!

Be sure to check out the upgrade guide for breaking changes in this release.

Important: as part of this release, we have promoted the new implementation of disk buffers (buffer.type = "disk_v2") to the default implementation (buffer.type = "disk"). Any existing disk buffers (disk_v1 or disk) will be automatically migrated. We have rigorously tested this migration, but recommend making a back up of the disk buffers (in the configured data_dir, typically in /var/lib/vector) to roll back if necessary. Please see the release highlight for additional updates about this migration.

In addition to the new features, enhancements, and fixes listed below, this release adds:

• Support for iteration has landed in VRL. Now you can dynamically map unknown key/value pairs in objects and items in arrays. This replaces some common use cases for the lua transform with the much more performant remap transform.
• New native event codecs for Vector. We are still rolling out the new codec support to all sinks, but this will allow sending events (logs, metrics, and traces) between Vector instances via transports like kafka rather than being limited to the gRPC vector source and sink.
• A new GCP PubSub (gcp_pubsub) source to consume events from GCP PubSub.
• A new websocket sink was added to send events to a remote websocket listener.
• New VRL functions for encrypting and decrypting data.

We also made additional performance improvements this release increasing the average throughput by up to 50% for common topologies (see our soak test framework).

This patch release contains a few fixes for regressions in 0.21.0.

Note: Please see the release notes for v0.21.0 for additional changes if upgrading from v0.20.X. In particular, the upgrade guide for breaking changes.

This patch release contains a few fixes for regressions in 0.21.0.

Note: Please see the release notes for v0.21.0 for additional changes if upgrading from v0.20.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.21.0!

Be sure to check out the upgrade guide for breaking changes in this release.

In addition to the new features, enhancements, and fixes listed below, this release adds:

• A new implementation of the VRL runtime as a Virtual Machine (VM). This new implementation improves performance over VRL’s current tree-walking interpreter implementation. For its initial release, this is an opt in feature (see the highlight for how) but will become the default VRL implementation in the future once it has stabilized. We encourage you to try it out and report any issues you find.
• A new redis source to complement the redis sink.
• Initial support for ingesting traces from the Datadog Agent (version < 6/7.33) and forwarding them to Datadog. We are working on adding support for newer Datadog Agents.
• The kubernetes_logs source has been rewritten to use the community supported kube-rs library. We expect that this will resolve some long outstanding bugs with Vector ceasing to process container logs. It also adds support for Kubernetes authentication token rotation.

We made additional performance improvements this release increasing the average throughput by up to 50% for common topologies (see our soak test framework).

Also, check out our new guide on using vector tap for observing events running through Vector instances

The Vector team is pleased to announce version 0.20.1!

This patch release contains a few fixes for regressions in 0.20.0.

Note: Please see the release notes for v0.20.0 for additional changes if upgrading from v0.19.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.20.0!

In addition to the new features, enhancements, and fixes listed below, this release includes a new opt-in disk buffer implementation that we hope will provide users with faster, more consistent, and lower resource usage buffer performance. We encourage you to opt-in during this beta period and give us feedback. See the beta disk buffer highlight article for more details including how to opt-in.

We also made additional performance improvements this release increasing the average throughput by 10-20% for common topologies (see our soak test framework).

Be sure to check out the upgrade guide for breaking changes in this release.

The Vector team is pleased to announce version 0.19.3!

This patch release contains a one bug fix for a regression in 0.19.0.

Note: Please see the release notes for v0.19.0 for additional changes if upgrading from v0.18.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.19.2!

This patch release contains a few bug fixes for regressions in 0.19.0.

Note: Please see the release notes for v0.19.0 for additional changes if upgrading from v0.18.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.19.1!

This patch release contains a few bug fixes for regressions in 0.19.0.

Note: Please see the release notes for v0.19.0 for additional changes if upgrading from v0.18.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.19.0!

In addition to the below features, enhancements, and fixes, we’ve been hard at work improving Vector’s performance and were able to move the needle 10-100% for most configurations in our soak test framework from the last release, v0.18.

Be sure to check out the upgrade guide for breaking changes in this release.

The Vector team is pleased to announce version v0.18.1!

This patch release contains a few bug fixes for regressions in v0.18.0.

Note: Please see the release notes for v0.18.0 for additional changes if upgrading from v0.17.X. In particular, the upgrade guide for breaking changes.

Bug Fixes:

• The new automatic namespacing feature broke usages of --config-dir when directories were present that did not match Vector’s config schema. Vector now just ignores these directories and only looks at known namespacing directories like sources/. #10173 #10177.
• The elasticsearch sink no longer logs a debug message for each event. #10117.
• The remap transform now only creates the .dropped output (as part of the new failed event routing feature) whenever reroute_dropped = true. #10152
• A change to internal telemetry had caused aggregated histograms emitted by the prometheus_exporter and prometheus_remote_write sinks to be incorrectly tallied. This was fixed. #10165

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 vector-agent and vector-aggregator charts. See the chart upgrade guide for how to transition from the old charts.

The Vector team is pleased to announce version v0.17.3!

This patch release contains a bug fix to ensure that Adaptive Concurrency Control is the default for all HTTP-based sinks, as was documented in the release notes for v0.17.0.

Note: Please see the release notes for v0.17.0 for additional changes if upgrading from v0.16.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version v0.17.2!

This release contains one additional bug fix to prefer fields decoded from the incoming event. This only mattered if you were using the new decoding feature with the json codec.

Note: Please see the release notes for v0.17.0 for additional changes if upgrading from v0.16.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version v0.17.1!

This release contains a few bug fixes from the v0.17.0 release to restore compatibility with existing source event decoding as well as a fix for the events_out_total metric where it was double the value it should have been.

Note: Please see the release notes for v0.17.0 for additional changes if upgrading from v0.16.X. In particular, the upgrade guide for breaking changes.

The Vector team is pleased to announce version 0.17.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release includes:

• One new component:
  • splunk_hec_metrics sink for sending metrics to Splunk
• Adaptive Concurrency enabled by default to maximize throughput for HTTP-based sinks
• An enhancement to the host_metrics to fetch memory and CPU metrics for cgroups
• New VRL functions: find, unique, and, a set of functions for dynamically looking up event fields, get, set, and remove.

It also contains a number of additional enhancements and bug fixes. Check out the highlights and changelog for more details.

Known issues

• events_out_total and processed_events_total ceased being published by sources and transforms. This will be fixed in a subsequent release, but these metrics have also been replaced by component_sent_events_total which is being implemented for all components.

The Vector team is pleased to announce version 0.16.1!

This release contains two bug fixes from the 0.16.0 release:

• Fixing an issue where Vector would crash when loading disk buffers
• Fixing an issue where the vector sink would incorrectly try to use http:// when tls was enabled

Note: Please see the release notes for 0.16.0 for additional changes if upgrading from 0.15.X. In particular, the upgrade guide for breaking changes.

Note: this release contains a regression for disk buffers. If you are using disk buffers, please install 0.16.1 instead.

The Vector team is pleased to announce version 0.16.0!

Be sure to check out the upgrade guide for breaking changes in this release.

This release includes:

• one new component:
  • nats source for collecting events from a NATS server
• support for HTTP proxies
• improved rate limit defaults for sinks
• the public release of the aggregator Helm chart beta

It also contains a number of additional enhancements and bug fixes. Check out the highlights and changelog for more details.

The Vector team is pleased to announce version 0.15.2!

This release contains a fix for vector validate to source environment variables indicating configuration location: VECTOR_CONFIG, VECTOR_CONFIG_YAML, VECTOR_CONFIG_JSON, and VECTOR_CONFIG_TOML.

In v0.15.0, we released a change the SystemD unit file to run vector validate before start-up as part of ExecStartPre. If users were using, for example, VECTOR_CONFIG in /etc/default/vector to pass the configuration location, this would result in Vector failing to boot.

See the release notes for 0.15.0 for additional changes if upgrading from 0.14.X.

The Vector team is pleased to announce version 0.15.1!

This release simply contains a bug fix for an RPM packaging regression in 0.15.0 where the RPM would not properly install if a previous version of the RPM was installed.

See the release notes for 0.15.0 for additional changes if upgrading from 0.14.X.

The Vector team is pleased to announce version 0.15.0!

This release includes a number of new components for collecting and sending data using Vector:

• datadog_events sink for sending events to Datadog’s event stream.
• dnstap source for collecting events from a DNS server via the dnstap protocol.
• fluent source for collecting logs forwarded by FluentD, Fluent Bit, or other services capable of forwarding using the fluent protocol such as Docker.
• logstash source for collecting logs forwarded by Logstash, Elastic Beats, or other services capable of forwarding using the lumberjack protocol such as Docker.
• azure_blob sink for forwarding logs to Azure’s Blob Storage.
• redis sink for forwarding logs to Redis.
• eventstoredb_metrics source for collecting metrics from EventStoreDB.

It also contains a number of additional enhancements and bug fixes. Check out the highlights and changelog for more details.

The Vector team is pleased to announce version 0.14.0!

This release includes a new exec source that can be used to execute arbitrary programs and use their output to generate events in Vector along with a number of enhancements.

Check out the changelog for more details.

The Vector team is pleased to announce version 0.13.0!

This release brings a new datadog_logs source to accept logs from dd-agents, a new gcp_stackdriver_metrics sink to send metrics to GCP Stackdriver, and a new subcommand, vector tap that allows for inspecting events flowing out of a component. It also brings a number of smaller enhancements, particularly around the Vector Remap Language used by our remap, filter, and route transforms.

Check out the highlights and changelog for more details.

The Vector team is pleased to announce 0.12.0. This release introduces the Vector Remap Language, an expression-oriented language designed for transforming observability data (logs and metrics) in a safe and performant manner.

Check out the VRL announcement post for more details as well as the highlights and changelog for a complete list of changes in 0.12.0.