[
https://issues.apache.org/jira/browse/JAMES-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140435#comment-17140435
]
Ioan Eugen Stan commented on JAMES-3251:
----------------------------------------
Logging can be reduced by using more appenders and streaming loggers to
different appenders.
Please use this configuration opion first before proposing the change in the
java source code of logging statements.
You can use a console and multiple file appenders.
You can log "org.apache.james.logger-that-you-deem-unworthy-of-basic-server" to
one of the more verbose file appenders or to dev null if you like.
This is documented on the slf4j website.
We should add this information to the docs under operations - how to manage
logging.
I've created a logging documentation for the developers.
They can be linked.
> Reduce INFO chatter
> -------------------
>
> Key: JAMES-3251
> URL: https://issues.apache.org/jira/browse/JAMES-3251
> Project: James Server
> Issue Type: Sub-task
> Reporter: David Leangen
> Priority: Major
>
> > To start, there is lots of "INFO" chatter that is not necessary.
> Maybe the "Basic Server operator" just needs to be aware of warnings & error,
> we can increase the logging level.
> We will need to better refine the "Basic server" application and split it
> from the advanced server one. Once we do it, we should be able to address all
> warnings & errors related to configuration.
> We "may" put to the INFO level like org.apache.james.GuiceJamesServer
> I believe a couples of annoying logs you mentioned should be addressed for
> all James server distributions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
