cassandra-commits mailing list archives

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


Ariel Weisberg commented on CASSANDRA-10241:

bq. I just didn't feel comfortable of enabling DEBUG logging by default, but if that was the
initial purpose of the ticket, and there are no objections, I'm +1. It will definitely make
us more cautious/thoughtful when adding debug messages in the future, and use TRACE level
for more verbose stuff (as it should be).
My thinking is that this still argues for having it on by default. If it's not on be default
how will we know if it is safe to turn on in production?

This isn't going to be trace/debug for everything right? I was thinking that specific loggers
would always log at trace/debug level and then we would groom the inputs so running them in
production is safe.

> 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