Vector v0.61.0 release notes

Vector now reports disk buffer lifecycle events during startup and configuration reloads. Each event is logged and increments the topology_disk_buffer_lifecycle_events_total counter with an event tag:

• removed: A removed sink still had data in its disk buffer, or Vector could not read how much data it held. The log says whether the sink’s current instance keeps draining the buffer in the background or whether the reload waits for it to finish.
• replacement_unreferenced: A changed sink no longer uses its previous disk buffer. If the reload succeeds, the new sink will not read any data left in the old buffer.
• unreferenced: A disk buffer in the data directory is not used by the current configuration. It may still be draining through a detached sink instance. If not, any data it holds is not being processed.

The mqtt sink now closes its broker connection when the sink stops, for example when a configuration reload removes or replaces it. Before, the connection stayed open, and the broker could repeatedly disconnect a replacement sink that used the same client ID.

Before it stops, the sink sends its queued messages and completes pending QoS exchanges. A configuration reload that waits for the sink, for example because the replacement reuses its buffer, also waits for this step. If the connection fails during this step, the sink stops without a reconnect and the reload continues.

address and routing.endpoints values in the vector sink that omit the scheme (for example, 127.0.0.1:6000 instead of http://127.0.0.1:6000) now default to https. Previously they defaulted to http unless TLS was enabled. The http default was deprecated in 0.59.0.

Endpoints that already specify a scheme, and scheme-less endpoints in configurations that enable TLS, are unaffected. A scheme-less endpoint pointing at a plaintext vector source now fails the TLS handshake.