Interesting, but not really what I was hoping for. Though truthfully, I'm not entirely sure what the use cases for logback-decoder are. My problem is that the app that I'm working on isn't amenable to conventional debugging, so use a "run with prodigious logging and sift through the wreckage" approach to many of my problems. It works, but it would work better if I had a tool, perhaps something along the lines of Lilith, or apparently logback-beagle, but not Eclipse based (I use IDEA) and capable of handling large volumes (Lilith was waaaaayyyy too slow). Thank you, Donald On Tue, Mar 12, 2013 at 12:52 PM, Tony Trinh <tony19@gmail.com> wrote:
Hi Donald,
Yes, there's currently a project for this task: logback-decoder [1]. It's been on hold for a while now since I've been completely swamped. Any help with this project is appreciated! Feel free to critique (note it's in rough form).
[1] https://github.com/qos-ch/logback-decoder
On Tue, Mar 12, 2013 at 10:45 AM, Donald McLean <dmclean62@gmail.com> wrote:
I noticed that there is an entry "write a tool for parsing log files" on the call for volunteers page. Is this an outstanding issue? Are there any current efforts going on in this area?