Hi Devs, the last email should have been for the whole dev list, not just Udara and Nirmal...
On Sun, May 25, 2014 at 8:19 PM, chris snow <chsnow...@gmail.com> wrote: > Hi Udara, Nirmal, > > I was assuming that the primary consumer of log files would be systems > administrators and not developers. Is this assumption incorrect? A sys > admin would definitely want enough information to diagnose the issue, but > they wouldn't want to see a stack trace or touch any code. > > Also, thinking on a tangent, if we have a multi-tenant installation where > the Stratos sys admin works for a different organisation to the tenant that > is deploying a cartridge, then how would the tenant diagnose deployment > issues? > > Many thanks, > Chris > > On 25 May 2014 19:38, "Udara Liyanage" <ud...@wso2.com> wrote: >> >> >> Hi Chris, >> >> The use of having a log is for someone to identify what went wrong, why >> went wrong, where it went wrong etc. >> For instance let's say there was a problem in deploying a cartridge. >> Showing a log like "error occurred while deploying a cartridge" is not use >> full very much. He wants to know what's wrong with the cartridge, in which >> line of the code it throws the error etc. >> >> Mostly developers are the ones who analyze the logs. So sufficient logs >> should be there to identify and fix problem. >> >> However I am OK with your suggestion for some extend that there should be >> a reasonable limit of error logs. >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. -- Check out my professional profile and connect with me on LinkedIn. http://lnkd.in/cw5k69
