Code name Vector Remap Language
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.
time
configuration
encoding.codec
where appropriate
healthchecks
option
parse_aws_alb_log
function
parse_aws_vpc_flow_log
function
gzip
& deflate
decompression
componentByName
query
parse_aws_cloudwatch_log_subscription_message
function
check_fields
conditions
get_env_var
Remap function
components
auth.access_key_id
and auth.secret_access_key
options
get_hostname
function
uptime
& boot_time
metrics
FileSourceMetricFile
sort
or
with nullable fields
gauge_add
atomics
events_in_total
& events_out_total
metrics
datadog_logs
sink
redact
function
ok
error handling function
parse_regex
and parse_regex_all
remap functions
parse_key_value
remap function
ignore_not_found
option
parse_common_log
function
parse_glog
function
tag_types_externally
function
processed_events_total
in topology for transforms
includes()
in_flight_limit
core_threads
for merge_and_fork
leveldb
compact after certain amount of deleted bytes
ipv6_to_ipv4
function allows ipv4 addresses to pass through
parse_grok
should error when it fails to parse
processed_events_total
after transform has processed event
/
as a valid escape target
vector
source and sink currently use the TCP protocol to transmit data. While this has
served users well, it presents operational challenges for large-scale deployments of Vector. Because
HTTP is widely used and easy to integrate into platforms like Kubernetes we will be moving these
components to the HTTP protocol.Sign up to receive emails on the latest Vector content and new releases
Thank you for joining our Updates Newsletter