+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" <nirmal070...@gmail.com> wrote: > >> +1 from me too. >> >> On Sun, Nov 9, 2014 at 7:03 PM, Isuru Haththotuwa <isu...@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/ >> >
