What happened while you were not looking.
A Windows notification is gone in seconds, the live charts look back three minutes, and the engine keeps only its last 256 events. The app remembers for you: every notification you can read back, a day of CPU and memory, and one page with everything that happened.
Fig. — The Events page: containers, images, volumes and networks together, newest first.
What you can do
The notifications you missed
A bell in the header with a count, and the last 200 notifications underneath. A click goes where the notification itself went.
Also what was never shown
Muted a container, or turned a kind of notification off? It still gets logged, greyed out, with the reason. Silent should mean it does not interrupt you, not that you never see it.
The last three in the tray
With the window closed is exactly when you miss one, and the system tray is where you look.
A day of CPU and memory
Measured every minute for every running container and kept for 24 hours, so it survives a restart of the app. A leak or a nightly spike is invisible in three minutes.
Per container and over everything
On the dashboard the two lines across all containers, on a container its own line with its memory limit underneath.
Memory that keeps climbing
Six hours of steadily rising memory puts a container on the attention card as a hint. A hint, not a notification: plenty of things use more memory for good reasons.
Everything on one page
Containers, images, volumes and networks together, newest first: started, stopped, crashed, out of memory, pulled, tagged, created, removed.
Narrow it down
Filter by kind, by name, by compose project and by period — everything, the last hour, today, last night. A crash stands out in red.
Longer than the engine remembers
Docker keeps 256 events for everything together.
With a few health-checked containers that reaches back minutes, not days: every check costs three events. The app follows the same stream it already uses for crash notifications and keeps its own history in its own files, per docker context.
Small on purpose
One point per five minutes, 200 notifications, 500 events.
Enough to draw a line and to answer "what happened last night", small enough to stay a file you never think about. Measuring happens once a minute for the whole app: the memory watch and the history share the same round.
All features