On Thu, Apr 21, 2016 at 9:49 AM, Paul Angus
wrote:
> Hey Daan,
>
> I understand from a purists point of view, but to me messages like:
>
> INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-113:ctx-56d9f9f2)
> Scan hung worker VM to recycle
>
> Are part of the inner workings of cloudstack, and
--Original Message-
From: Frank Louwers [mailto:[email protected]]
Sent: 21 April 2016 08:14
To: [email protected]
Subject: Re: CloudStack Logging
Hi Paul,
I’d love to see improvement in that area! Especially for my operational admins,
the biggest issue we face is this:
- Someo
Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Daan Hoogland [mailto:[email protected]]
Sent: 20 April 2016 23:12
To: [email protected]
Subject: Re: CloudStack Logging
Paul,
Your classification of levels seems right. I wouldn't say WARN mean
d:2, nodeIP:10.2.0.6
> DEBUG [c.c.c.ClusterManagerImpl] (Cluster-Heartbeat-1:ctx-0bccd078) Detected
> management node left, id:2, nodeIP:10.2.0.6
>
>
>
>
> Kind regards,
>
> Paul Angus
>
> Regards,
>
> Paul Angus
>
> [email protected]
tx-0bccd078)
> Detected management node left, id:2, nodeIP:10.2.0.6
>
>
>
>
> Kind regards,
>
> Paul Angus
>
> Regards,
>
> Paul Angus
>
> [email protected]
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeb
:[email protected]]
Sent: 20 April 2016 11:32
To: [email protected]
Subject: RE: CloudStack Logging
Hello,
I have a question what is the criteria that you are going to follow to decide
the log record importance. Who is the user that you will design the logging
process for. Is it
put in mind when designing the logging process.
Sent from my Samsung Galaxy smartphone.
Original message
From: Paul Angus Date:
20/04/2016 1:01 PM (GMT+04:00) To: [email protected],
[email protected] Subject: RE: CloudStack Logging
Hi Simon,
My gut says
Paul Angus
[email protected]
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Simon Weller [mailto:[email protected]]
Sent: 19 April 2016 21:51
To: [email protected]; [email protected]
Subject: Re: CloudSta
Paul,
Are you wanting for focus on logs on releases later than a particular version
(e.g. 4.6)?
- Si
From: Paul Angus
Sent: Tuesday, April 19, 2016 10:55 AM
To: [email protected]; [email protected]
Subject: RE: CloudStack Logging
No
eblue
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf Of
Will Stevens
Sent: 19 April 2016 16:53
To: [email protected]
Cc: [email protected]
Subject: Re: CloudStack Logging
Thanks Paul. Are you looking for only logs with erro
> @shapeblue
>
> -Original Message-
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Will Stevens
> Sent: 19 April 2016 16:40
> To: [email protected]
> Cc: [email protected]
> Subject: Re: CloudStack Logging
>
Will Stevens
Sent: 19 April 2016 16:40
To: [email protected]
Cc: [email protected]
Subject: Re: CloudStack Logging
I like this initiative Paul. I just wanted to check with you. Do you know if
there is any confidential information like credentials or the like that is
logged in
n Tue, Apr 19, 2016 at 11:34 AM, Paul Angus
wrote:
> Hi All,
>
> I'm running an initiative to improve CloudStack logging. I'm going to be
> analysing logs and re-categorising the DEBUG, INFO, WARN and ERROR where
> appropriate such that we can reduce the default logging
Hi All,
I'm running an initiative to improve CloudStack logging. I'm going to be
analysing logs and re-categorising the DEBUG, INFO, WARN and ERROR where
appropriate such that we can reduce the default logging level to INFO without
losing important troubleshooting information, wh
I am studying the logging process used by CloudStack and came accross
the configuration file that is used by Log4j. What is confusing to me is
that all the resources is stating that the "log4j-cloud.xml" is
supposed to be the file used to confiugre the logging, but what I have
noticed is that
15 matches
Mail list logo
