cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12696) Allow to change logging levels based on components
Date Wed, 28 Sep 2016 10:23:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Podkowinski updated CASSANDRA-12696:
-------------------------------------------
    Labels: lhf  (was: )
    Status: Patch Available  (was: In Progress)

> 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.3.4#6332)

Mime
View raw message