no-external

Automate local log file rotation by renaming active log files to a versioned format and truncating the original file. This prevents logs from growing indefinitely and consuming disk space on your server.

Log file truncation clears the contents of an active log file after archiving it to a versioned format. You need it for filesystem maintenance when log files reach a specific size threshold and risk consuming available disk space.

You can rotate application logs entirely within the local filesystem without external dependencies or network connectivity. The process operates locally, requiring only read and write access to the configured log file path.

The best way to maintain system health locally is to apply log rotation, which renames the current log file to a versioned suffix like .log.1 and truncates the original file to free up disk space.

Local log rotation does not require external API calls or external tools to function. It performs state management and file truncation entirely within the local filesystem using standard read and write access.