Hi
@ANON4,
My answers to your questions:
1) SAS Logs is your number one place to look out for in-case of any issues or troubleshooting.
Removing them or deleting them can make you loose on those information. Instead having an archiving policy for all your SAS Tier logs would be an ideal solution.
Every organization depending upon their policy has different time window for storing/archiving of logs. It could be anything starting from 30 days to even six months.
I would suggest you to follow standard policy for archiving. You can create a simple bash script to help you with this process.
Link for sample script here:
https://tekkiehead.com/linux-shell-script-to-archive-log-files.html/2) (i) I don't think running cleanwork utility will increase your log file size.
(ii) Does your code do any Metadata related operations like Create/Update/Delete/Auth etc.? Any update done to Metadata is logged depending upon the logging you have enabled for Metadata server.
If you think after running your hourly EG Script, logs for Metadata has increased, you can review the logs for any updates based on your codes.
Here is the link to check for detailed logging enabled in metadata or not.
https://documentation.sas.com/?docsetId=bisag&docsetTarget=p0hchigzq8wvtrn1tnllswe7jmqb.htm&docsetVe...3) As suggested in Point#1 better to have archiving policy instead of deleting the logs daily.
Hope this helps!
Thanks!