[
https://issues.apache.org/jira/browse/CLOUDSTACK-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745081#comment-14745081
]
ASF subversion and git services commented on CLOUDSTACK-8645:
-------------------------------------------------------------
Commit 34caa694d0a788d649408d83719e87110d098410 in cloudstack's branch
refs/heads/master from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34caa69 ]
Merge pull request #821 from wido/libvirt-rbd-logging
CLOUDSTACK-8645: Improve logging of RBD functionality in KVMA simple commit
which changes a couple of log lines.
* pr/821:
CLOUDSTACK-8645: Improve logging of RBD functionality in KVM
Signed-off-by: Wido den Hollander <w...@widodh.nl>
> 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)
