[
https://issues.apache.org/jira/browse/OFBIZ-11956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178459#comment-17178459
]
James Yong commented on OFBIZ-11956:
------------------------------------
+1
Most timing-related logs should be finer than info level.
> Re-thinking the Log-Level
> -------------------------
>
> Key: OFBIZ-11956
> URL: https://issues.apache.org/jira/browse/OFBIZ-11956
> Project: OFBiz
> Issue Type: Improvement
> Components: content, framework
> Affects Versions: Trunk
> Reporter: Benjamin Jugl
> Priority: Minor
>
> 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.
> # {{ScreenFactory |I| Got %s screens in 0.004s from: %s}}
> # {{ConfigXMLReader |I| controller loaded: 0.001s, 115 requests, 59 views in
> file: %s}}
> # {{ModelService |I| Set default value [%s] for parameter [%s]}}
> # {{ServiceEcaCondition |I| From Field (%s) is not found in context for %s,
> defaulting to null.
> }}
> # {{ServiceEcaCondition |W| doRealCompare returned null, returning false}}
> # {{DataResourcePermissionServices.xml#genericDataResourcePermission line
> 69] }}
> # {{DataResourcePermissionServices.xml#genericDataResourcePermission line
> 73]}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
