Is there a way to make sure that the logs on the server don’t get deleted and they stay there permanently? I know you can untick “delete”, however these are still removed when you refresh the page or login and logout.
Is it also possible for a platform owner or a super user to be able to view all these runs across the server to check everything is running as expected?
you can find the settings regarding to your question in our documentation here.
com.knime.server.job.max_lifetime=<duration with unit, e.g. 60m, 36h, or 2d> [RT]
Specifies the time of inactivity, before a job gets discarded (defaults to 7d).
Negative numbers disable forced auto-discard. com.knime.server.job.webportal.max_lifetime=<duration with unit, e.g. 60m, 36h, or 2d> [RT]
Specifies the time of inactivity, before a job started from the WebPortal gets discarded (defaults to the same value as com.knime.server.job.max_lifetime), negative numbers disable forced auto-discard. Only change this value in case you are having issues with a single setting for all job types.
The options can be set in the file <knime-server-repository>/config/knime-server.config .
Just to clear up, is it possible to keep logs up to 12 or 24 months?
Also, is there a way to automatically have the tick box for “delete” unticked? Or removed entirely to prevent members of our team deleting processes after they have ran?
I am afraid there is no configuration option available that would allow you to change the default behavior (meaning setting the checkbox ‘unticked’ as default).
Regarding to your other question, may I ask why do you want to have / keep jobs in memory for such a long time? Keeping the jobs in memory for such a long time could cause heavy performance issues.
Okay I understand. For us it would be from a business case point of view, to be able to see what jobs have been ran and by which members of the team they have been ran.
This workflow allows to view all jobs that were ran on the KNIME Server. Admin Server Credentials are required to execute this workflow, though.
In the result table under ‘owner’ column you can see the username who had run the workflow.
By regularly running this workflow and saving the result, I think you can get the information you need.