mikejones Much of this really depends on what you plan to do with the logs collected from a regulatory or security reason. See below
mikejones I am managing my own web server and I have never deleted any of its logs, from anything running on the website.
Is this Linux ? From memory, it is.
LOGROTATE should already be active on that system (providing it is configured) - in most cases, logs are stored within
/var/logs/ and you should see iterations of the older log files that have been automatically rotated with a view to keeping the log sizes sane, and at the same time, providing a mechanism for archive
mikejones For deleting logs, what's the best way to manage the constant clean up?
Again, this really depends on how long you plan to retain those logs, and what purpose that will be for. Logging is generally useful in order to track a particular issue or error, but for the most part, rarely used unless there is an issue to track. LOGROTATE once configured correctly will handle the rotation and retention of logs. After a period of time, older logs will "drop off" and no longer be available.
If disk usage is an issue (as it would be in setups such as Amazon Web Services), and any subsequent backups are increasing owing to the size of the logs, it makes sense to set a policy in order to retain what you need, and discard the rest. I can provide further detail on this if I'm able to understand what the requirements and setup are.