When a container operating in Kubernetes records its logs in stdout or stderr stream, they are picked up by the kubelet service operating at that node and transferred to the container engine to be operated based on the logging driver fixed at Kubernetes. In most cases, the Docker container logs will be stored in your host's directory/var/log/containers.
When the container breaks or restarts, the kubelet stores its logs in the node. To prevent these files from consuming all host storage, the log path must be set to a node. Kubernetes does not offer built-in log rotation, but this functionality is available on many tools, such as Docker log-opt, standard file senders, or a simple custom cron function. When the container is removed from the site, so do its associated log files.
With 01Cloud, you can aggregate and report on logs retrieved from all services across all server nodes. It showcases the total view of the health and performance of an application and infrastructure stack, enabling developer teams and system administrators to more easily diagnose and rectify issues. Users can analyze these logs to discover errors, system start-up messages, updates, and application errors.