[
https://issues.apache.org/jira/browse/LOG4NET-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708306#action_12708306
]
Ron Grabowski commented on LOG4NET-154:
---------------------------------------
Thanks! That was easier than I thought..
I wonder if there would be any speed benefits to communicating to LocationInfo
that no one needs stack information so don't bother collecting any...i.e. all
the layouts are just simple %message%newline. Plus in Release mode the stack
info may be unreliable. The simple solution would be to add a special value to
the repository's properties. A more complicated solution would track each
pattern layout and only activate stack gathering if at least one appender
requested it.
> Add a StackTracePatternConverter to display method calls leading up to log
> message
> ----------------------------------------------------------------------------------
>
> Key: LOG4NET-154
> URL: https://issues.apache.org/jira/browse/LOG4NET-154
> Project: Log4net
> Issue Type: New Feature
> Reporter: Ron Grabowski
> Fix For: 1.2.11
>
> Attachments: StackTracePatternConverter.zip
>
>
> Modify LocationInfo to save StackTrace information and make it available as
> StackTracePatternConverter to display call stack leading up to the log
> message:
> log.Debug("Item Saved");
>
> [%stackTrace{3}] %message%newline
> [default_aspx.btnSubmit_Click > productController.Save >
> productService.Save] Item Saved
> This will probably be a slow pattern converter on par with other LocationInfo
> derived pattern converters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
