Skip to main content

Hi,

the application log retention setting has been made into a select instead of a input field. This means we can only select between 30, 60, 90, 365 days and indefinitely. Because we have a lot of process flows that create a lot of logs the IAM becomes slow and unresponsive.

And yes, i totally agree that working with scheduled system flow that run every 2 seconds should be avoided but life.

Can we change this back making this field into a normal INT field again? That would give each developer the flexibility needed. It’s not like the value isn’t stored in the database as a int so it’s only a cosmetical change. 

Or at least take out the constraint limiting the values that we can put in the global_settings table in that field.

 

Hi Bas,

Recently we have release a platform improvement (20250117 - Improve performance of process flow schedule log) that adds an Index to the process_flow_schedule_log table. We and several other customers have seen a huge performance increase after deploying it.

For the upcoming 2025.1, we have split the Application log retention setting into two, creating a new retention setting specially for the Process flow schedule log table. Whilst it still is a dropdown list, you can now set it as low as 3 days to ensure you can monitor your applications may any problems arise regarding system flow runs. 

The Application log tables feed the Environment interaction monitor, which contains several cube views that show the amount of failures and successes over a period of time of at least a month, hence the 30 days minimum. If we would allow a lower value, the cube views would have be changed as well. Feel free to create an idea for that.

Reply


Terms & ConditionsCookie settings