[
https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738983#comment-14738983
]
Benedict commented on CASSANDRA-10241:
--------------------------------------
If we are talking about:
* _shrinking_ the current regular INFO (and up) output, to only very high level
state changes and important information
* moving DEBUG statements that cannot be logged as standard to TRACE
* expanding DEBUG with low traffic high information statements, and including
everything we remove from INFO (such as all of the flush / compaction
information)
* logging DEBUG (and up) to a separate file
Then I'm more onboard with the idea (I'll not again I'm not opposing it, just
putting my view across), as there is a bit more clarity to the distinction, and
it might still make sense even in a future world of higher quality/verbosity
debug logging. I'm still not sure it's exactly necessary, though.
> 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)
