[
https://issues.apache.org/jira/browse/CASSANDRA-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Podkowinski updated CASSANDRA-12696:
-------------------------------------------
Resolution: Fixed
Reviewer: Chris Lohfink
Status: Resolved (was: Ready to Commit)
Thanks! Merged as c1f6239.
I don't think keeping the list of classes in sync will be that much of an issue
in practice. I've went through the list again that I've created a year ago and
all classes still exist and seem to be still relevant. But patching the list
should not be an issue in case something's missing.
> 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: [email protected]
For additional commands, e-mail: [email protected]
