[
https://issues.apache.org/jira/browse/JAMES-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144718#comment-17144718
]
David Leangen commented on JAMES-3251:
--------------------------------------
After a bit of struggle (and a few small issues outstanding), I took a crude
approach in order to resolve this issue:
# Reduced all logging to the "Operator's Console" for now (since almost all is
not useful anyway)
## Excludes those entries (in the comment above) that are rogue
# Logging to a rolling file appender for diagnostics (in case something goes
wrong)
I included plenty of comments in the configuration file in case a curious
Operators decides to look at it. I think it should be ok. (Will attach to this
issue.)
Next steps:
# Determine from a top-down level (instead of combing through the existing
logs) what types of entries would be useful for an Operator
# If they exist, ensure that they are included in the CONSOLE appender
# If they don't exist or don't express the information well, file issues to
get those entries included / updated
It may be a good idea to actually go through the DEBUG logs to determine if the
system is actually running well. :)
I have updated only in the sandbox for now. I do not yet know how the Basic
Server will be included in the main code base (if at all??).
Even though this has not yet been included in the codebase, I am resolving this
issue.
> Reduce INFO chatter for Basic Server
> ------------------------------------
>
> Key: JAMES-3251
> URL: https://issues.apache.org/jira/browse/JAMES-3251
> Project: James Server
> Issue Type: Sub-task
> Reporter: David Leangen
> Priority: Major
> Attachments: logback.xml
>
>
> In the context of the *Basic Server*, based on the principle that the
> Operator does not know (and does not need to know) the internals of the
> system:
> # Reduce the Operator's log output to the absolute minimum (in one way or
> another)
> # Ensure that any output is useful and actionable in the Basic context
> # Consider what to do with regard to diagnostic information that, in the
> case of a problem, would allow experienced James Developers to assist when
> necessary
> This issue focuses only on point #1 in the above list. Once that is
> completed, we should consider the other two points.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
