cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10241) Keep a separate production debug log for troubleshooting
Date Wed, 09 Sep 2015 22:11:46 GMT


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

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
** This is not natively supported by logback though, we would need to add the [janino|]
# 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:
>             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

View raw message