Identify which domain logs are large and whether an incident or reporting process needs them preserved. Estimate daily growth, available space and required retention. Local rotation is not a substitute for a protected off-server archive when longer retention is required.

1. Open the domain Logs page, then Log Rotation or the equivalent control under Manage Log Files.
2. Enable rotation and choose an available size-based or time-based policy suited to the volume. A very small threshold can create many files without providing useful retention.
3. Set the number of retained files and compression where supported. Consider how many days that actually represents at normal and peak traffic.
4. Review any email-delivery option carefully. Logs may contain sensitive data and large attachments, so a secure archive destination can be more appropriate than routine email.
5. Save the policy and observe the next scheduled rotation. Preserve required older logs before reducing the retention count.

Suppose a size-based policy keeps eight rotated files. If normal traffic produces one rotation each day, those files cover roughly eight days. If a traffic spike produces four rotations per day, the same count may cover only about two days. The active file and varying request volume make these estimates approximate.

Check actual file timestamps after the policy has run. Choose retention from the investigation window you need and the observed growth, then confirm there is enough storage. Compression reduces occupied space but does not turn a file-count policy into a guaranteed time-based archive. Preserve required incident evidence separately before reducing the count.

Confirm rotated files appear, compression works and new requests continue to reach the active log. Check disk usage after the normal rotation cycle rather than expecting an immediate drop at the moment you save.

If storage continues growing, inspect application logs, mail logs and backup archives that are outside this domain policy. Do not manually truncate files needed for an active incident without an evidence copy. If rotation fails, review permissions and server maintenance errors with the administrator instead of repeatedly changing thresholds.

• Diagnosing website errors with the Plesk log browser
• Checking disk space and traffic usage in Plesk
• Creating and downloading a full subscription backup in Plesk
• Adding supported Apache and nginx directives in Plesk

• Plesk: Log Files
• Plesk: 12377655504023 How To Change Log Rotation Settings For A Domain In Plesk