Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A124D17449 for ; Wed, 9 Sep 2015 22:44:46 +0000 (UTC) Received: (qmail 21536 invoked by uid 500); 9 Sep 2015 22:44:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 21507 invoked by uid 500); 9 Sep 2015 22:44:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 21490 invoked by uid 99); 9 Sep 2015 22:44:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 22:44:46 +0000 Date: Wed, 9 Sep 2015 22:44:46 +0000 (UTC) From: "Paulo Motta (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10241) Keep a separate production debug log for troubleshooting MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737741#comment-14737741 ] Paulo Motta commented on CASSANDRA-10241: ----------------------------------------- bq. Or is there more to it than that? My initial patch didn't populate {{debug.log}} at all, unless the operator manually set the {{TROUBLESHOOTING_LEVEL}} property to {{DEBUG}} or {{TRACE}}, on {{logback.xml}}. bq. If it's not on be default how will we know if it is safe to turn on in production? Advanced operators and consultants could start using it by manually turning it on, and if no issues found after a few versions, then we could enabled it by default later. bq. This isn't going to be trace/debug for everything right? Right, only on the aforementioned packages. I don't have strong feelings about this, so I'm fine with either way. I think that with the {{AsyncAppender}} we shouldn't have significant impact with debug logging on by default. > 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)