I always notice that the container uses relatively a lot of CPU continously, I am not really sure what its doing, but maybe its just the task of parsing the logs. In any case its using far more than Nginx Proxy Manager itself, which is a bit weird, since I would expect NPM to have more to do than GoAccess.
Anyway, as I am not looking at GoAccess that often (max once a week) I now manually start the container when I need it, and stop it when Im done. But that becomes a bit cumbersome.
So what I really would prefer is an option to only start parsing the logs as soon as I visit the web UI of GoAccess, and that it goes to sleep after no activity for 15 minutes or so. Ofcourse that will make visiting the page a lot slower, but as I am not often doing that its no problem.
That way I could leave the container running 24/7 without it taking any CPU. Would you be willing to implement such an "on-demand" option?
Perhaps it could only run once an hour or once a day normally, but when the site is loaded it will refresh once with the latest info, and have a refresh button to pull any new logs after?
I always notice that the container uses relatively a lot of CPU continously, I am not really sure what its doing, but maybe its just the task of parsing the logs. In any case its using far more than Nginx Proxy Manager itself, which is a bit weird, since I would expect NPM to have more to do than GoAccess.
Anyway, as I am not looking at GoAccess that often (max once a week) I now manually start the container when I need it, and stop it when Im done. But that becomes a bit cumbersome.
So what I really would prefer is an option to only start parsing the logs as soon as I visit the web UI of GoAccess, and that it goes to sleep after no activity for 15 minutes or so. Ofcourse that will make visiting the page a lot slower, but as I am not often doing that its no problem.
That way I could leave the container running 24/7 without it taking any CPU. Would you be willing to implement such an "on-demand" option?