Delete old log files

[Former Member]

I'm looking for a functionality to delete old log files from an application deployed on the nw cloud but I wasn't able to spot it yet. Neither the neo sdk tools nor the web page https://account.netweaver.ondemand.com/ seem to provide such a functionality. As a workaround I'd also be happy with some kind of logrotate functionality where I can manually trigger a rename of the existing logs so I can start with a new and empty log file.

[Former Member · Accepted solution]

Hi Tobias,

what log files exactly do you want to delete? Are you using custom log files? The standard files (e.g. ljs_trace.log) are taken care of. They are rotated and cleaned up on the local VMs after they are transferred to the central log server from where you can download them via the account page or the console client. On the central server the files are deleted automatically after 7 days.

Best regards,

Nikolay

[Former Member · Accepted solution]

Hi Nikolay,

yes I'm talking about the ljs_trace.log files. Is there any mechanism to trigger the rotation and transfer to the central log server manually? Or is it possible to have one log file per application run? Currently if I stop and restart an app the ljs_trace is always appended to the previous run.

Best regards,

Tobias

[Former Member · Accepted solution]

Hi Tobias,

there is no way to trigger rotation manually at the moment. The logs are transferred when they are logged in the file. Rotation on the central server is done per size (50MB) and per date. You get also different log files per VM id. If the VM you start takes the same VM id from the pool the logs will be appended to the old file. You can distinguish the different runs in one file by the log headers - after restart a new log header is logged.

Can you describe your use case briefly? What is the background for this requirement?

Best regards,

Nikolay

[Former Member · Accepted solution]

Hi Nikolay,

there is no special use case here. It was just my laziness/curiosity regarding the evaluation of log files. When diagnosing errors in an app one may has to repeatedly change, package and redeploy it. If this happens in an iterative manner and with some detailed logging level like debug one will quickly get a large log file which isn't a pleasure to analyze. This is the only reason for my question so I don't think its really a requirement. And since I've found the error in my app there isn't even a reason for my question any longer 😉

Best regards,

Tobias