vasilmkd / docker-stats-monitor Goto Github PK

thanks for the excellent utility!
Currently neither the dockerfile nor the command line to run the container configure the memory use. Native image application will by default have the following configuration (in the environment with enough resources):
-Xmx -- max heap size -- not limited by default.
-Xmx -- young generation size -- 256M by default.

the consequence of that is that currently, by default, before the young gen is filled there's no GC happening. So the application (and the docker container) will consume at least 256M on a machine where docker has enough resources.

You can configure it on the application level by passing -Xmx and -Xmn to the native image, for example in the dockerfile

ENTRYPOINT [ "/server", "-Xmx64M" ]

or using docker options to limit memory available to the container, for example:

docker run -d --name monitor --memory=64m --memory-swap=64m -p "8080:8080" -v /var/run/docker.sock:/var/run/docker.sock vasilvasilev97/docker-stats-monitor

Then the container will work the same way, but the memory usage will stay at a fraction of 256M to which it grows now.

Before:

After:

Hello,

This project is really good alternative for lots of those paid options out there. however it's missing one critical feature which is data persistence. without it if the server or docker updates then the data is gone.

Is there any plans to support such use case in the future?

Thank you.

Ok so it does seem to be reproducible. Here is what I did:

1. Ran the monitor.
2. Started another container which was running a Java process which was suspended waiting for the debugger to attach.
3. Set a breakpoint to occur when an exception is thrown.
4. Attached the debugger.
5. Waited for the stats of that new container to be shown in the monitor.
6. Allowed the process to continue and throw the exception which causes the process and the container to exit with a non-zero exit code.

Originally posted by @steinybot in #41 (comment)

Thanks for the app, it is really handy.

I was wondering if there is a way to prevent the graph from being removed when the container exits? I am using it to monitor a container which is getting killed by the OOM killer and it would be nice to keep the graph around after it has been killed.