System node logs are not zipping automatically leading to high DB memory occupation (On Premise Customers) - Support and Troubleshooting

System node logs are not zipping automatically leading to high DB memory occupation (On Premise Customers) Description The System Logs provides a variety of logs that you can use to troubleshoot and debug transactions and events that take place within the instance. However if you find the system logs (Usually the logs directory is "/glide/nodes/ /logs/" not compressed/zipped automatically in your instance, it leads to high DB memory utilization. Resolution The scheduled job ' Clean logs ' is responsible to zip the log files and delete them over a period.

Please ensure the following:

Clean logs job is up and running. It is running on all the nodes. Trigger type is set to 'Interval' State is ready. Repeat is set to 1 day. Script shows : 'GlideLogCleanup.clean();' Refer below sample screenshot showing the above steps.

Additional Information The instance creates compressed archives of system logs every two days and purges log archives after 21 days. You can download log file archives and view them with System Logs > Log File Download. Select a log archive from the list, and then click Download log under Related Links to open or save the archive. Note: Log files are only available for the node you are currently logged into. To see the currently logged into node, navigate to System Diagnostics > Stats.

For more information, you can refer to the documentation: Use the log file browser