[
https://issues.apache.org/jira/browse/GUACAMOLE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043500#comment-18043500
]
Mike Jumper commented on GUACAMOLE-2181:
----------------------------------------
Also, if individual log messages involve multiple lines (common with the JDBC
extensions), the log itself can become difficult to parse. It would be far
better for multi-line messages to include formatting that clarifies which lines
are continuations of previous messages.
> Clarify source/style of log messages
> ------------------------------------
>
> Key: GUACAMOLE-2181
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-2181
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
> Reporter: Mike Jumper
> Priority: Minor
>
> The logging of the Guacamole web application relies on class naming to
> identify the source of each message, which is too developer-centric and can
> make troubleshooting opaque. Administrators are not expected to have an
> understanding of which classes are involved with which extensions.
> The logs should clearly show which extension is producing which log messages,
> without requiring the reader to know which classes are in which extensions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
