[Feature] Improve Container monitoring#928
Conversation
|
Interesting idea. This layout could work well when we get SMART data added. Let me get the next release out and I'll circle back on these PRs. |
It's ready when you are! This should cover all the open requests for docker related things. If you want to discuss any or the changes feel free to hook me up on Discord, I’m there under the same username. |
|
Thanks, you've been on a tear lately. I'll try to start reviewing these in the next few days. |
|
Happy to be able to contribute 😄 , Take your time in reviewing. |
|
@henrygd I might leave the conflict for this one up to you. Try to solve them in the last few days, but kept running into weird problems with data mappings etc. At least this way you can make it in the way you want 😅 |
|
No worries, not a problem. |
|
Will this work with Services on Docker Swarm? And if not, could I request such a feature? |
There are open request for notifications for containers. As that touches the Alert engine, it will handled separately. |
|
Any update on this? I am really interested in this feature. |
Me too +1 |
|
Sorry, this is still near the top of my todo list, but I've been very busy. Will get to it as soon as I can. |
|
FYI @svenvg93, you have merge conflicts |
|
I can fix the conflicts if Sven can't get to it. Not a problem at all 👍 |
|
I will try to find some time to solve them. With the restructure and all the other changes in the meantime I might start fresh 😅 |
|
@henrygd I fixed all the conflicts, hopefully without breaking anything ;) |
|
Hyped for the release! 😊 |
|
Working on this now. I'm tweaking / adapting everything and updating how we're storing container data to make it a bit more efficient. I'll probably roll it out over the next handful of releases rather than all at once. |
- Add new /containers route with virtualized table showing all containers across systems - Implement container stats collection (CPU, memory, network usage) with health status tracking - Add container logs and info API endpoints with syntax highlighting using Shiki - Create detailed container views with fullscreen logs/info dialogs and refresh functionality - Add container table to individual system pages with lazy loading - Implement container record storage with automatic cleanup and historical averaging - Update navbar with container navigation icon - Extract reusable ActiveAlerts component from home page - Add FooterRepoLink component for consistent GitHub/version display - Enhance filtering and search capabilities across container tables
|
@henrygd Thanks for your work on v0.14 and the amazing additions to the container monitoring. Is there still anything you need from this PR or can I close it? |
|
@svenvg93 I merged on a different branch so I can continue to reference it. Thanks again for your contributions! |
|
@henrygd Is there anything I can do to help getting the other items of this PR across the finish line? Don't mind breaking it up in smaller PRs If that makes it easier for you. |
|
@svenvg93 Yes, that would definitely help, thank you. I've been jumping around on different features and haven't had time to see it all the way through. |
No worries, I will slowly start working on it. |
- Add new /containers route with virtualized table showing all containers across systems - Implement container stats collection (CPU, memory, network usage) with health status tracking - Add container logs and info API endpoints with syntax highlighting using Shiki - Create detailed container views with fullscreen logs/info dialogs and refresh functionality - Add container table to individual system pages with lazy loading - Implement container record storage with automatic cleanup and historical averaging - Update navbar with container navigation icon - Extract reusable ActiveAlerts component from home page - Add FooterRepoLink component for consistent GitHub/version display - Enhance filtering and search capabilities across container tables
This PR refactors the way how the container stats are displayed and collected. This should improve the container monitoring and implement/solve most of the open issues.
System StatsandDocker StatsDocker Network I/OwithDocker Network UsageCONTAINER_EXCLUDEenvironment variable. For exmaple:CONTAINER_EXCLUDE="runner-,temp-,test-,jenkins-"When there are no containers;
When there are containers
Schermopname.2025-07-01.om.07.39.48.mp4
I will update the docs after merging to cover any changes later on.