Your system automatically collects and manages logs to help you monitor activity, troubleshoot issues, and maintain system health. It gathers logs from containers running across your nodes and processes them for viewing and retention. Logs are rotated regularly to prevent storage overflow—older files are compressed, archived, and eventually deleted if unmodified for a set period (typically 90 days).
You’ll encounter two main types of logs: access logs, which record requests made to services or applications, and server logs, which include internal system and application activity. Each log file follows a consistent naming convention that includes the pod name, namespace, container name, and container ID. All logs are stored under:
/var/log/storage/
Logs are stored in plain text and timestamped using UTC in the format YYYY-MM-DDTHH:MM:SS. They are retained for up to 90 days and checked hourly to determine if they exceed the size limit or meet the rotation interval. When rotated, logs are compressed and moved to an archive directory:
/var/log/storage/archived/date