Why Log rotation in Nginx? - Purpose & Use Cases

The Big Idea

What if your server suddenly stops because logs filled up the disk? Log rotation saves you from that nightmare.

The Scenario

Imagine you run a busy website using nginx. Every day, your server creates huge log files recording every visitor and error. Without managing these logs, they keep growing and take up all your disk space.

The Problem

Manually checking and deleting or moving log files is slow and easy to forget. If logs grow too big, your server can slow down or crash. Also, important information might get lost if you delete logs carelessly.

The Solution

Log rotation automatically renames and compresses old log files and starts fresh ones. This keeps logs organized, saves disk space, and ensures your server runs smoothly without manual work.

Before vs After

✗ Before

rm /var/log/nginx/access.log
mv /var/log/nginx/access.log.1 /backup/

✓ After

logrotate /etc/logrotate.d/nginx

What It Enables

Log rotation lets your server handle logs efficiently, so you never run out of space and always keep important data safe.

Real Life Example

A busy online store uses log rotation to keep daily sales logs manageable and quickly find issues without worrying about disk space running out.

Key Takeaways

Manual log management is slow and risky.

Log rotation automates organizing and compressing logs.

This keeps servers stable and logs accessible.