[logback-dev] [JIRA] Commented: (LBCLASSIC-325) Filtering out selected stack trace frames

Tomasz Nurkiewicz (JIRA) noreply-jira at qos.ch
Sat Mar 17 23:27:26 CET 2012

    [ http://jira.qos.ch/browse/LBCLASSIC-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12381#action_12381 ] 

Tomasz Nurkiewicz commented on LBCLASSIC-325:

I created a small proof-of-concept: https://github.com/nurkiewicz/logback/tree/LBCLASSIC-325 and wrote a little bit more about the problem: http://nurkiewicz.blogspot.com/2012/03/filtering-irrelevant-stack-trace-lines.html.

> Filtering out selected stack trace frames
> -----------------------------------------
>                 Key: LBCLASSIC-325
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-325
>             Project: logback-classic
>          Issue Type: New Feature
>          Components: appender, layout
>            Reporter: Tomasz Nurkiewicz
>            Assignee: Logback dev list
>            Priority: Minor
> Many frameworks and libraries like Spring or EJB are introducing hundreds of synthetic method invocations (AOP, dynamic proxies, CGLIB-generated classes, etc.) They are irrelevant for most of the time and only cluttering the stack traces printed by Logback.
> It would be nice to have possibility to filter (possibly by providing a set of patterns in logback.xml) each stack trace line and skip selected ones. Similar feature is implemented in some IDEs, see: http://blogs.jetbrains.com/idea/2010/07/console-folding-customization.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list