cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8645) Make better use of different loglevels like INFO, WARN and ERROR instead of DEBUG
Date Tue, 15 Sep 2015 08:57:46 GMT


ASF subversion and git services commented on CLOUDSTACK-8645:

Commit 4f409a7c173d2a2dd0e400dcd1ba426a1af66425 in cloudstack's branch refs/heads/master from
[;h=4f409a7 ]

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:
>             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

View raw message