[
http://jira.qos.ch/browse/LBCORE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11836#action_11836
]
Pascal Leclercq commented on LBCORE-117:
----------------------------------------
I have exactly the same requirements. This feature will be extremly usefull I
think. Is there any workaround for the time being ?
I think smthg can be done using Evaluators and/or filters but I don't know
where to find the last N logging event.
> Supply an appender that collects N events on all levels and dumps them to the
> output when an ERROR is logged
> ------------------------------------------------------------------------------------------------------------
>
> Key: LBCORE-117
> URL: http://jira.qos.ch/browse/LBCORE-117
> Project: logback-core
> Issue Type: New Feature
> Components: Appender
> Reporter: Aaron Digulla
> Assignee: Logback dev list
>
> For many applications, it's not necessary to log at the levels DEBUG and
> TRACE all the time. In fact, we usually only do this to be able to debug
> ERROR events.
> It would be great if there was an appender that would only collect a
> configurable number of events internally until a message of level ERROR or
> above is logged. At this time, the appender should dump it's internal state
> to the log and reset the internal state.
--
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
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev
