Hi Chris, On Sun, May 25, 2014 at 11:14 PM, chris snow <chsnow...@gmail.com> wrote:
> Hi Nirmal, I was thinking it is OK to log one or two lines or information, > but not a stack trace? > Wouldn't this approach cause us to lose data which will help to determine what went wrong if an issue occurs? IMHO we should log stack traces as well in case of an error. But I agree that verbosity of error logging should be controlled, else it will actually hide the real problem among lines and lines of errors. On 25 May 2014 16:28, "Nirmal Fernando" <nirmal070...@gmail.com> wrote: > >> Chris, >> >> You suggest even not to log the exception in log file? If that's the >> case, how could one track the issue? >> >> >> On Sun, May 25, 2014 at 4:28 PM, chris snow <chsnow...@gmail.com> wrote: >> >>> I'm having some issues with Stratos spawning instances due to >>> downstream issues with my IaaS. However, I'm seeing a lot of >>> exception stack traces in my stratos log file. >>> >>> The first question that comes to mind while looking through the logs >>> is "has an error occurred within the Stratos code base?". >>> >>> Should we be hiding exceptions from users unless something the >>> exception is because something has gone wrong with Stratos code? >>> >> >> >> >> -- >> Best Regards, >> Nirmal >> >> Nirmal Fernando. >> PPMC Member & Committer of Apache Stratos, >> Senior Software Engineer, WSO2 Inc. >> >> Blog: http://nirmalfdo.blogspot.com/ >> >
