jochen 3d8b52c9f4 docker: say where the runtime's event history begins, so a short history never reads as a quiet one (hq issue 348) ...

docker_events asked for three hours across the 2026-10-09 resolver outage on the control node answered
zero events: the runtime keeps only its last ~256 events in memory, and health-check execs filled them
with the last ten minutes. The answer now carries held, oldest_held and complete, and a history line
when the window reaches further back than what the runtime still holds. The type filter moves into the
tool, since the history's start is only known from all of it.

2026-10-09 15:04:45 +02:00

..

docker-tools

docker: say where the runtime's event history begins, so a short history never reads as a quiet one (hq issue 348)

2026-10-09 15:04:45 +02:00