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
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
Check out the highlights and changelog for more details.
events_in_totalinternal metric to sources
routetransform can now process metrics
is_TYPEhelper functions such as
Logtype to expose the log event as JSON
parse_regexnow suppresses the numeric capture groups by default but they can be re-added via
numeric_groups: truein the function call
channelquery parameter rather than just the
abortstatement to halt processing
tapsubcommand to view events flowing out of a component
parse_nginx_logfunction for parsing common nginx log formats
to_regexfunction to convert strings to regexes
--no-topologyhas been removed from
case_sensitiveparameter for string matching functions (like
starts_with) were updated to default to case sensitive matching to match docs
httpsources to handle multi-part files
Shortly you will be able to iterate over data in VRL to:
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.
This was mentioned in the release notes for 0.11.0, but didn’t quite make it for 0.12 as anticipated. We do expect it to be released in the next few months.
Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter