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.
We’ve heard from a number of users that they’d like improved delivery guarantees for events flowing through Vector. We are working on a feature to allow, for components that are able to support it, to only acknowledging data flowing into source components after that data has been sent by any associated sinks. For example, this would avoid acknowledging messages in Kafka until the data in those messages has been sent via all associated sinks.
This release includes the groundwork for this feature including support in a number of source and sink components that support acknowledgements, but it has not yet been fully documented. We expect to officially release this with 0.15.0.
We are hard at work at expanding the ability to run Vector as an aggregator in Kubernetes. This will allow you to build end-to-end observability pipelines in Kubernetes with Vector. Distributing processing on the edge, centralizing it with an aggregator, or both. If you are interested in beta testing, please join our chat and let us know.
We do expect this to be released in the next few months.
topto use more accurate
.to an array
redactfunction to VRL
--no-default-features --features apibuild failure
hostto remote address