[OFBIZ-11956] Re-thinking the Log-Level

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: Trunk, Upcoming Branch
• Component/s: content, framework
• Assignee: Unassigned
• Reporter: Benjamin Jugl
• Created: 13/Aug/20 08:31
• Updated: 11/Jan/22 08:48

Description

The following log messages have all a log level of "info" or "warning". In our experience, however, this is a very large source of noise during operation. The messages are in my opinion only of interpretation, if it is necessary to examine the signal flow in case of error. I know that there is a difference of opinion on this subject, so I have listed the places that we have put on Verbose in our projects. I am looking forward to hearing your thoughts on this topic.

1. ScreenFactory |I| Got %s screens in 0.004s from: %s
2. ConfigXMLReader |I| controller loaded: 0.001s, 115 requests, 59 views in file: %s
3. ModelService |I| Set default value [%s] for parameter [%s]
4. {{ServiceEcaCondition |I| From Field (%s) is not found in context for %s, defaulting to null.
   }}
5. ServiceEcaCondition |W| doRealCompare returned null, returning false
6. {{DataResourcePermissionServices.xml#genericDataResourcePermission line 69] }}
7. DataResourcePermissionServices.xml#genericDataResourcePermission line 73]