Log message order when vector shuts down is confusing

[tronboto]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

Basically, there is a log message claiming that Vector has stopped but then after that is printed, there are still more Waiting on running components INFO level log messages. During post hoc analysis, this makes it difficult to determine when vector actually exited.

I've noticed it in our installations but you can also see it in #24300 :

2025-11-25T16:15:49.919276Z  INFO vector::signal: Signal received. signal="SIGTERM"
2025-11-25T16:15:49.919592Z  INFO vector: Vector has stopped.
2025-11-25T16:15:49.919942Z DEBUG sink{component_kind="sink" component_id=stdout component_type=console}: vector::utilization: Couldn't send utilization start wait message. component_id=ComponentKey { id: "stdout" } error="Closed(..)"
2025-11-25T16:15:49.920012Z DEBUG sink{component_kind="sink" component_id=stdout component_type=console}: vector::utilization: Couldn't send utilization start wait message. component_id=ComponentKey { id: "stdout" } error="Closed(..)"
2025-11-25T16:15:49.920075Z  INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="stdout, systemd_udp_socket_activation" time_remaining="59 seconds left"
2025-11-25T16:15:50.523278Z DEBUG sink{component_kind="sink" component_id=stdout component_type=console}: vector::utilization: Couldn't send utilization start wait message. component_id=ComponentKey { id: "stdout" } error="Closed(..)"
2025-11-25T16:15:50.523364Z TRACE vector: Beep.
2025-11-25T16:15:51.531153Z TRACE vector: Beep.
2025-11-25T16:15:52.560313Z TRACE vector: Beep.
2025-11-25T16:15:53.515193Z TRACE vector: Beep.
2025-11-25T16:15:54.518591Z TRACE vector: Beep.
2025-11-25T16:15:54.929487Z  INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="stdout, systemd_udp_socket_activation" time_remaining="54 seconds left"
2025-11-25T16:15:54.936062Z TRACE source{component_kind="source" component_id=systemd_udp_socket_activation component_type=socket}: vector_common::internal_event::bytes_received: Bytes received. byte_size=34 protocol=udp

Configuration

Version

vector 0.51.1 (x86_64-unknown-linux-gnu 44c8f1c 2025-11-13 15:16:05.303418529)

Debug Output

Example Data

No response

Additional Context

No response

References

No response