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 Thu, 10 Sep 2015 16:12:47 GMT


Ariel Weisberg commented on CASSANDRA-10241:

I would say that more or less that is the goal. The details on how to make that happen are
flexible. Once we have the capability to have two logs with different levels of detail I want
to iteratively improve on the contents. I would characterize this task as provide the capability
and do no harm. I think that opting in log statements by package, or level is too broad and
skips the step of grooming the logging.

That requires a point where we can evaluate the log. I don't know yet where that will come
from. When I did direct support it was obvious because I was heavily invested in the quality
of the log when working with users. I think as we get deeper into working with CVH tests we
will be more aware of the quality of log output as it will be the only thing we have access
to after a failure and that is when things will start to improve.

So right now I want to create the path for that to happen.

> 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