You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2017/08/28 19:58:00 UTC
[jira] [Updated] (CASSANDRA-12696) Allow to change logging levels
based on components
[ https://issues.apache.org/jira/browse/CASSANDRA-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa updated CASSANDRA-12696:
-----------------------------------
Status: Ready to Commit (was: Patch Available)
> Allow to change logging levels based on components
> --------------------------------------------------
>
> Key: CASSANDRA-12696
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12696
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Minor
> Labels: lhf
> Attachments: 12696-trunk.patch
>
>
> Currently users are able to dynamically change logging configuration by using {{nodetool setlogginglevel <class> <level>}}. Unfortunately this requires to know a bit about the Cassandra package hierarchy and gathering all the involved packages/classes can be tedious, especially in troubleshooting situations. What I'd like to have is a way to tell a user to "_when X happens, enable debug logs for bootstrapping/repair/compactions/.._" by simply running e.g. {{nodetool setlogginglevel bootstrap DEBUG}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org