cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10241) Keep a separate production debug log for troubleshooting
Date Thu, 10 Sep 2015 16:24:47 GMT


Benedict commented on CASSANDRA-10241:

Well, currently that is pretty much what we use the regular log output for. Judging by the
fact most users don't attach it when filing bugs, I suspect we're its main consumers. It's
the first port of call for debugging bug reports, and despite its lack of excellence is often
sufficient to diagnose. 

A concerted effort to improve its quality is definitely a goal I can get behind, whether or
not it gets segregated.

> 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