Default logging levels should be updated to create less noise. Additivity doubles the trace output for the user
STEPS TO REPRODUCE:
Expected Results: The logging levels to be set to a configuration that does not cause excessive entries in the logs, those should be reset upon upgrade to default values
Actual Results:
This fills the logs excessively with messages as follows:
INFO 2022-06-22 22:57:35,485 [Event Handler pool-6-thread-8] auth.event (clarity:admin:22785727__9E1D329D-AE67-4BE3-8724-D4C730D765A1:none) SECURITY POLICY CHECK FAILURE has occurred for [objectType=RECORD permissionCode=WRITE userName=admin] by admin
INFO 2022-06-22 22:57:35,485 [Event Handler pool-6-thread-8] auth.event (clarity:admin:22785727__9E1D329D-AE67-4BE3-8724-D4C730D765A1:none) SECURITY POLICY CHECK FAILURE has occurred for [objectType=RECORD permissionCode=TimeSheetAccess userName=admin] by admin
INFO 2022-06-22 22:57:35,485 [Event Handler pool-6-thread-8] auth.event (clarity:admin:22785727__9E1D329D-AE67-4BE3-8724-D4C730D765A1:none) SECURITY POLICY CHECK FAILURE has occurred for [objectType=RECORD permissionCode=APPROVE userName=admin] by admin
3. Also Detect Log Configuration Changes Automatically must be set to Yes by Default
Release : 16.0.2, 16.0.3
Workaround: Reset the logging levels manually:
1. Set the trace.server.selective.user to not be Additive
2. Set the Priority for auth.event to Error
3. Save and restart the services if Detect Changes Automatically on the Logs page is not set
This is DE65546, fixed in 16.1.0 and 16.0.3.1