You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kurt Greaves (JIRA)" <ji...@apache.org> on 2018/04/16 06:30:00 UTC
[jira] [Commented] (CASSANDRA-14326) Handle verbose logging at a
different level than DEBUG
[ https://issues.apache.org/jira/browse/CASSANDRA-14326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439032#comment-16439032 ]
Kurt Greaves commented on CASSANDRA-14326:
------------------------------------------
As a user/operator I can't see the need to split out a subset of logs to a verbose-system.log.
If it helps the operator it should just be in the system.log. If those logs are making system.log too noisy then thought needs to go into better log messages. A bit of code refactoring for clearer/less noisy log messages is preferable to just shipping them off to another file.
More log files is just a nightmare for operators in my experience, and most will just end up pumping them all into journald/[insert log service here] defeating the purpose anyway.
The proposals so far mostly just sound to me like keeping the debug logging but with a different name. Debug logs are for developers, not operators.
> Handle verbose logging at a different level than DEBUG
> ------------------------------------------------------
>
> Key: CASSANDRA-14326
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14326
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Alexander Dejanovski
> Priority: Major
> Fix For: 4.x
>
>
> CASSANDRA-10241 introduced debug logging turned on by default to act as a verbose system.log and help troubleshoot production issues.
> One of the consequence was to severely affect read performance in 2.2 as contributors weren't all up to speed on how to use logging levels (CASSANDRA-14318).
> As DEBUG level has a very specific meaning in dev, it is confusing to use it for always on verbose logging and should probably not be used this way in Cassandra.
> Options so far are :
> # Bring back common loggings to INFO level (compactions, flushes, etc...) and disable debug logging by default
> # Use files named as verbose-system.log instead of debug.log and use a custom logging level instead of DEBUG for verbose tracing, that would be enabled by default. Debug logging would still exist and be disabled by default in the root logger (not just filtered at the appender level).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org