I already did. See my reply above
On Mon, Oct 13, 2014 at 11:50 AM, Isuru Haththotuwa
wrote:
>
>
> On Mon, Oct 13, 2014 at 11:13 AM, Isuru Perera wrote:
>
>> We should remove the duplicate class name from logs
>>
> +1
>
>>
>> On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne
>> wrote:
>>
>>>
>>
On Mon, Oct 13, 2014 at 11:13 AM, Isuru Perera wrote:
> We should remove the duplicate class name from logs
>
+1
>
> On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne wrote:
>
>>
>>> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
>>> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
>>
We should remove the duplicate class name from logs
On Mon, Oct 13, 2014 at 9:15 AM, Imesh Gunaratne wrote:
>
>> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
>> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
>> %c appears twice, which lets the class name to logged twice
>>
>> This
>
>
> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
> %c appears twice, which lets the class name to logged twice
>
> This is the convention used in carbon server logs.
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member,
committed to both container-autoscaling and master branches
On Sat, Oct 11, 2014 at 8:06 AM, Rajkumar Rajaratnam
wrote:
>
>
> On Sat, Oct 11, 2014 at 7:59 AM, Sajith Kariyawasam
> wrote:
>
>> Hi,
>>
>> Haven't noticed this until now :)
>>
>> in og4j.appender.CARBON_LOGFILE.layout.ConversionPatt
On Sat, Oct 11, 2014 at 7:59 AM, Sajith Kariyawasam wrote:
> Hi,
>
> Haven't noticed this until now :)
>
> in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
> [%d] %P%5p *{%c}* - %x %m* {%c}*%n
> %c appears twice, which lets the class name to logged twice
> I think we should
Hi,
Haven't noticed this until now :)
in og4j.appender.CARBON_LOGFILE.layout.ConversionPattern=TID: [%T] [%S]
[%d] %P%5p *{%c}* - %x %m* {%c}*%n
%c appears twice, which lets the class name to logged twice
I think we should remove that, thanks Raj or pointing out!
Thanks,
Sajith
On Sat, Oct 11,
Hi,
On Sat, Oct 11, 2014 at 6:44 AM, Nirmal Fernando
wrote:
> Why do you want to remove TID part? It stands for Tenant ID.
>
I didn't meant to remove it from code base. I wanted to do it locally in my
running setup so that I can clearly observe the scaling logs. It is very
lengthy now. And the
Why do you want to remove TID part? It stands for Tenant ID.
All these can be configured via log4j.properties files corresponding
Appenders.
On Sat, Oct 11, 2014 at 6:41 AM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Can we configure the logging format?
>
> Currently we are logging in the format like
Hi,
Can we configure the logging format?
Currently we are logging in the format like below;
TID: [0] [STRATOS] [2014-10-11 06:39:05,722] INFO
{org.apache.stratos.autoscaler.rule.RuleLog} - Running minimum rule:
[kub-cluster] KubGrp1 [cluster] myphp.php.domain
{org.apache.stratos.autoscaler.rul
10 matches
Mail list logo