[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743409#comment-14743409
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8645:
--------------------------------------------

GitHub user wido opened a pull request:

    https://github.com/apache/cloudstack/pull/821

    CLOUDSTACK-8645: Improve logging of RBD functionality in KVM

    A simple commit which changes a couple of log lines.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/wido/cloudstack libvirt-rbd-logging

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/821.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #821
    
----
commit 7884dc8e6010ee68a93b927a4f4821239dcefa42
Author: Wido den Hollander <w...@widodh.nl>
Date:   2015-09-14T11:50:53Z

    CLOUDSTACK-8645: Improve logging of RBD functionality in KVM
    
    A simple commit which changes a couple of log lines.

----


> Make better use of different loglevels like INFO, WARN and ERROR instead of 
> DEBUG
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8645
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8645
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: Future
>         Environment: All CloudStack components
>            Reporter: Wido den Hollander
>              Labels: debug, log4j, logging, loglevel
>             Fix For: Future
>
>
> Currently most of the code uses s_logger.debug() for logging events.
> Running on logging level INFO or WARN makes CloudStack logs almost unusable 
> since almost no interesting information comes by.
> We should improve the logging on various points by replacing DEBUG with INFO, 
> WARN or ERROR to what seems appropriate.
> This should be done continuously, this isn't something which can be fixed 
> with one big patch, commit or PR.
> While working on the code you'll spot these issues and can fix them when 
> needed.
> On big environments for example the management server log in level DEBUG 
> becomes almost unusable due to the high volume of messages coming by.
> There is certainly more to improve on logging, but this is a start.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to