Answer the question
In order to leave comments, you need to log in
How to save docker-compose inter-session logs and watchdog?
Colleagues, tell me
1) how to organize the storage of logs between docker-compose sessions with fading records?
2) how to detect memory/process eaters?
My hosts reboot frequently, docker-compose starts with the host. While docker-compose is running, the logs are available via portainer or docker logs, but after a reboot, nothing remains of the previous session. Logging in compose is configured as local-file with a limit on the size and number of rotation-substitutions. The hosts are small, I can't allow the logs to swell endlessly, the hdd is small.
In addition to these nuances, today I discovered that something ate all the memory (the last frozen picture with 100% of memory remained on the system indicator in debian), what exactly is unknown =(
Answer the question
In order to leave comments, you need to log in
1) raise ElasticSearch for collecting and processing logs
2) limit memory for containers.
It's a bit more complicated - you need to raise the monitoring of all hosts
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question