You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Isuru Haththotuwa <is...@apache.org> on 2014/11/09 19:03:17 UTC
Reduce the Verbosity of Logging
Hi Devs,
I think we need to $subject, specially in the messaging component. In
single JVM, since we have only one Topology model, and three sets of
updaters, there are multiple logs indicating that Topology has already been
updated.
For an example when a service created, there will be multiple level logs
saying the service has been already created, since there are three threads
updating the topology. IMO, after the initial successful update to
topology, we can use debug logs to indicate that the service has already
been created.
In general, this will reduce the number of default log lines and thus will
reduce the difficulty to analyze the default log.
WDYT?
--
Thanks and Regards,
Isuru H.
+94 716 358 048* <http://wso2.com/>*
Re: Reduce the Verbosity of Logging
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
+1 for doing this..This will help debugging issues specially with composite
application, since multiple clusters associated with an application, the
flow cannot be predicted using the logs since logs include publisher as
well as subscriber for the single JVM.
On Sun, Nov 9, 2014 at 11:33 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has already been
> updated.
>
> For an example when a service created, there will be multiple level logs
> saying the service has been already created, since there are three threads
> updating the topology. IMO, after the initial successful update to
> topology, we can use debug logs to indicate that the service has already
> been created.
>
> In general, this will reduce the number of default log lines and thus will
> reduce the difficulty to analyze the default log.
>
> WDYT?
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: Reduce the Verbosity of Logging
Posted by Isuru Haththotuwa <is...@apache.org>.
Created [1] to track this, and did some initial changes.
[1]. https://issues.apache.org/jira/browse/STRATOS-962
On Mon, Nov 10, 2014 at 10:53 AM, Isuru Perera <is...@wso2.com> wrote:
> +1. We need change such redundant log messages to "DEBUG" level and keep
> only the required logs in "INFO" level.
>
> On Sun, Nov 9, 2014 at 11:33 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi Devs,
>>
>> I think we need to $subject, specially in the messaging component. In
>> single JVM, since we have only one Topology model, and three sets of
>> updaters, there are multiple logs indicating that Topology has already been
>> updated.
>>
>> For an example when a service created, there will be multiple level logs
>> saying the service has been already created, since there are three threads
>> updating the topology. IMO, after the initial successful update to
>> topology, we can use debug logs to indicate that the service has already
>> been created.
>>
>> In general, this will reduce the number of default log lines and thus
>> will reduce the difficulty to analyze the default log.
>>
>> WDYT?
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
> * <http://wso2.com/>*
>
>
>
Re: Reduce the Verbosity of Logging
Posted by Isuru Perera <is...@wso2.com>.
+1. We need change such redundant log messages to "DEBUG" level and keep
only the required logs in "INFO" level.
On Sun, Nov 9, 2014 at 11:33 PM, Isuru Haththotuwa <is...@apache.org>
wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has already been
> updated.
>
> For an example when a service created, there will be multiple level logs
> saying the service has been already created, since there are three threads
> updating the topology. IMO, after the initial successful update to
> topology, we can use debug logs to indicate that the service has already
> been created.
>
> In general, this will reduce the number of default log lines and thus will
> reduce the difficulty to analyze the default log.
>
> WDYT?
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Reduce the Verbosity of Logging
Posted by Chamila De Alwis <ch...@wso2.com>.
+1
However when reducing log entries IMO it should be taken in to
consideration if the particular log entries are actually redundant or if
they are representing unique code paths, which can help in initial
"debugging" itself.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Nov 10, 2014 at 8:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
> +1 Isuru.
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Nov 10, 2014 1:24 AM, "Nirmal Fernando" <ni...@gmail.com> wrote:
>
>> +1 from me too.
>>
>> On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa <is...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I think we need to $subject, specially in the messaging component. In
>>> single JVM, since we have only one Topology model, and three sets of
>>> updaters, there are multiple logs indicating that Topology has already been
>>> updated.
>>>
>>> For an example when a service created, there will be multiple level logs
>>> saying the service has been already created, since there are three threads
>>> updating the topology. IMO, after the initial successful update to
>>> topology, we can use debug logs to indicate that the service has already
>>> been created.
>>>
>>> In general, this will reduce the number of default log lines and thus
>>> will reduce the difficulty to analyze the default log.
>>>
>>> WDYT?
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* <http://wso2.com/>*
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
Re: Reduce the Verbosity of Logging
Posted by Udara Liyanage <ud...@wso2.com>.
+1 Isuru.
Touched, not typed. Erroneous words are a feature, not a typo.
On Nov 10, 2014 1:24 AM, "Nirmal Fernando" <ni...@gmail.com> wrote:
> +1 from me too.
>
> On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa <is...@apache.org>
> wrote:
>
>> Hi Devs,
>>
>> I think we need to $subject, specially in the messaging component. In
>> single JVM, since we have only one Topology model, and three sets of
>> updaters, there are multiple logs indicating that Topology has already been
>> updated.
>>
>> For an example when a service created, there will be multiple level logs
>> saying the service has been already created, since there are three threads
>> updating the topology. IMO, after the initial successful update to
>> topology, we can use debug logs to indicate that the service has already
>> been created.
>>
>> In general, this will reduce the number of default log lines and thus
>> will reduce the difficulty to analyze the default log.
>>
>> WDYT?
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* <http://wso2.com/>*
>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
Re: Reduce the Verbosity of Logging
Posted by Nirmal Fernando <ni...@gmail.com>.
+1 from me too.
On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa <is...@apache.org> wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has already been
> updated.
>
> For an example when a service created, there will be multiple level logs
> saying the service has been already created, since there are three threads
> updating the topology. IMO, after the initial successful update to
> topology, we can use debug logs to indicate that the service has already
> been created.
>
> In general, this will reduce the number of default log lines and thus will
> reduce the difficulty to analyze the default log.
>
> WDYT?
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Reduce the Verbosity of Logging
Posted by Imesh Gunaratne <im...@apache.org>.
+1
On Sunday, November 9, 2014, Isuru Haththotuwa <is...@apache.org> wrote:
> Hi Devs,
>
> I think we need to $subject, specially in the messaging component. In
> single JVM, since we have only one Topology model, and three sets of
> updaters, there are multiple logs indicating that Topology has already been
> updated.
>
> For an example when a service created, there will be multiple level logs
> saying the service has been already created, since there are three threads
> updating the topology. IMO, after the initial successful update to
> topology, we can use debug logs to indicate that the service has already
> been created.
>
> In general, this will reduce the number of default log lines and thus will
> reduce the difficulty to analyze the default log.
>
> WDYT?
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* <http://wso2.com/>*
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos