You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by chris snow <ch...@gmail.com> on 2014/05/25 12:58:42 UTC
exception logging
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?
Re: exception logging
Posted by chris snow <ch...@gmail.com>.
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 <ch...@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
Re: exception logging
Posted by chris snow <ch...@gmail.com>.
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.
>
Re: exception logging
Posted by Udara Liyanage <ud...@wso2.com>.
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.
Re: exception logging
Posted by Isuru Haththotuwa <is...@apache.org>.
Hi Chris,
On Sun, May 25, 2014 at 11:14 PM, chris snow <ch...@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" <ni...@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 <ch...@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/
>>
>
Re: exception logging
Posted by Nirmal Fernando <ni...@gmail.com>.
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 <ch...@gmail.com> 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" <ni...@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 <ch...@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/
>>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: exception logging
Posted by chris snow <ch...@gmail.com>.
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" <ni...@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 <ch...@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/
>
Re: exception logging
Posted by Nirmal Fernando <ni...@gmail.com>.
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 <ch...@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/