[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737688#comment-14737688
]
Paulo Motta commented on CASSANDRA-10241:
-----------------------------------------
bq. my inclination would be to say that the debug log should be a superset of
the normal info log
I think that makes sense. Implementation-wise we would have the following
options to support that (afaik):
# Comment-out the {{ASYNCDEBUGLOG}} appender reference on the root-logger, and
let operators uncomment if they want to enable {{debug.log}} with logs from all
levels.
# Conditionally add the {{ASYNCDEBUGLOG}} appender to the root-logger based on
a configuration property.
** This is not natively supported by logback though, we would need to add the
[janino|http://logback.qos.ch/setup.html#janino] dependency.
# Always have the {{ASYNCDEBUGLOG}} appender enabled on the root-logger, so
{{INFO}} messages are always duplicated on both {{system.log}} and
{{debug.log}}.
If [~aweisberg] doesn't have any other suggestion, or objection, I think 1 is
the best approach.
> Keep a separate production debug log for troubleshooting
> --------------------------------------------------------
>
> Key: CASSANDRA-10241
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10241
> Project: Cassandra
> Issue Type: New Feature
> Components: Config
> Reporter: Jonathan Ellis
> Assignee: Paulo Motta
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> [~aweisberg] had the suggestion to keep a separate debug log for aid in
> troubleshooting, not intended for regular human consumption but where we can
> log things that might help if something goes wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
