Larry Smith commented on Improvement CONSPLUG-35
While trying your suggestion of "By setting level on the logger tree, you can filter OUT events which have already reached logback-beagle" I see the following:

Ran my application and traces are outputted to logback-beagle as expected.
Then in the logger tree I set one of my packages to level ERROR and all data on the beagle window is cleared. Then continuing on with your statement about "disable an "existing" filter" I reset the package back to inherit. Still see nothing on the beagle window.

Each action against the beagle tree causes information in the window to disappear, and a rerun of the application is required to see it again. BTW, this is beagle 1.1.3.

Thank you for listening, (I do understand that it is a one way communication from logback to beagle) all of my comments pertain to beagle being able to filter out what it displays.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira