rg
Subject: Re: [discuss] CloudStack logging
Something that could be interesting also is to remove VR and systemVMs logs
from the cloudstack-management.log and have them into a separate files. I'm
still not sure of those logs are traps only when there is problems, if it's the
case it mak
>
> > Kind regards,
> >
> > Paul Angus
> >
> > Regards,
> >
> > Paul Angus
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> > @shapeblue
> >
> > -
nd regards,
>
> Paul Angus
>
> Regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
Regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: 14 April 2016 15:04
To: Paul Angus ; dev@cloudstack.apache.org
Subject: Re: [disc
n, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Chaz PC [mailto:dreeems4e...@hotmail.com]
Sent: 14 April 2016 16:01
To: dev@cloudstack.apache.org
Subject: RE: [discuss] CloudStack logging
I am confused about the configuration file there two files one is named
Log4j-cloud.xml The
PM (GMT+04:00) To:
dev@cloudstack.apache.org Subject: Re: [discuss] CloudStack logging
Based on the namespace log level can be set. It needs to be configured in the
log4j.
Check client/tomcatconf/log4j-cloud.xml.in in the source code and you will get
an idea.
-Koushik
: Thursday, April 14, 2016 7:29 PM
To: dev@cloudstack.apache.org
Subject: Re: [discuss] CloudStack logging
Do you have to recompile in order to turn off the logging for a specific
package or class? If yes, that is a show stopper for almost everyone...
If it only requires a management server restart, that
_
> From: Paul Angus
> Sent: Thursday, April 14, 2016 9:06 AM
> To: Wido den Hollander; dev@cloudstack.apache.org
> Subject: RE: [discuss] CloudStack logging
>
> Grabbing a couple of examples - these should be debug - I can't 'do'
> anything with this infor
Sent: Thursday, April 14, 2016 9:06 AM
To: Wido den Hollander; dev@cloudstack.apache.org
Subject: RE: [discuss] CloudStack logging
Grabbing a couple of examples - these should be debug - I can't 'do' anything
with this information.
INFO [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJo
Paul Angus
Regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: 14 April 2016 15:04
To: Paul Angus ; dev@cloudstack.apache.org
Subject: Re:
> Op 14 april 2016 om 14:49 schreef Paul Angus :
>
>
> Hi All
>
> I think that we can all agree that CloudStack logs are very difficult to read,
> especially for operational staff.
>
> I believe that the primary reason for this is that a large amount of what
> should be INFO level events are c
Do you have to recompile in order to turn off the logging for a specific
package or class? If yes, that is a show stopper for almost everyone...
If it only requires a management server restart, that is more realistic.
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue G
On Thu, Apr 14, 2016 at 3:41 PM, Will Stevens
wrote:
> Is there an easy way to do that Daan, or is it a tedious task you just have
> to power through?
>
It is hard work, mostly tedious, sometimes hilarious and most definitely
devops! It certainly wouldn't classify as development.
--
Da
Is there an easy way to do that Daan, or is it a tedious task you just have
to power through?
I agree this initiative would be helpful.
On Apr 14, 2016 9:04 AM, "Daan Hoogland" wrote:
> I largely agree with just one sneer to the operators amongst us: the level
> can be set on a per package and e
I largely agree with just one sneer to the operators amongst us: the level
can be set on a per package and even class basis. So you can work through
disabling anoying logging step by step. Makes sense to keep looking at the
source in the meanwhile to make sure sensible diagnostics remains available
15 matches
Mail list logo
