Vector v0.19.0 release notes

VRL now allows for writing multi-line string literals by ending the line with a backslash (\).

Example:

.thing = "foo \
bar"

assert(.thing == "foo bar")

A couple of enhancements have been made to the influxdb_logs sink to modify how Vector encodes events.

A measurement config field was added to allow overriding the measurement name (previously hardcoded to vector). Along with this the namespace option was made optional as measurement can be used to set the full name directly.

For example:

[sinks.log_to_influxdb]
type = "influxdb_logs"
measurement = "vector-logs"
endpoint = "http://localhost:9999"

Now outputs events like:

vector-logs,metric_type=logs,host=example.com message="hello world",size=10 {timestamp}

A metric_type config field was added to allow customizing the metric type (previously hardcoded to log).

For example:

[sinks.log_to_influxdb]
type = "influxdb_logs"
measurement_type = "foo"
endpoint = "http://localhost:9999"

Now outputs events like:

ns.vector,metric_type=foo,host=example.com message="hello world",size=10 {timestamp}

VRL has added new functions for interacting with event metadata.:

• get_metadata_field("key")
• set_metadata_field("key", "value")
• remove_metadata_field("key")

Right now, the only event metadata that is accessible is Datadog API keys (datadog_api_key) or Splunk HEC channel tokens (splunk_hec_token) that are associated by the source, but we expect metadata use-cases to grow.

This can be used with, for example, CSV enrichment tables to lookup the datadog_api_key to use with events based on other metadata.