Hi Chris, If we consider jclouds scenario, having jclouds exception in stack trace helps us to get a clue as to what went wrong. If we remove that, we might need to ask the user to reproduce the issue, with jclouds logs enabled. But wouldn't that be an inconvenient thing?
On Sun, May 25, 2014 at 11:14 PM, chris snow <[email protected]> wrote: > Hi Nirmal, I was thinking it is OK to log one or two lines or information, > but not a stack trace? > On 25 May 2014 16:28, "Nirmal Fernando" <[email protected]> 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 <[email protected]> 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/ >> > -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
