Vector v0.27.0 release notes

Vector has added support for tracking component memory allocations to help users understand which components may be allocating more memory than expected. This is an opt-in feature, due to ~20% performance overhead, available by passing --allocation-tracing when running Vector. When enabled, the internal_metrics source will publish new component_allocated_bytes, component_allocated_bytes_total, and component_deallocated_bytes_total metrics. These are will then also be viewable in vector top.

There is a caveat to the reported metrics in that memory passed between components is not tracked as allocations. For example, if a source allocates memory to store incoming events, those events are passed along to a downstream component, the memory will still appear as though owned by the source component that allocated it. We hope to improve this in the future to track memory passed between component boundaries.

See the announcement blog post for more details!

VRL no longer rejects querying an object returned by the merge function. This fixes programs that look like:

.object.key = "some value"
. |= parse_key_value!(del(.message))
.object.key = "some other value" # previously would error