@Bastien Lamoureux - You should only have one entry for MsgTrkInputPath and use semi-colon (;) to separate the different paths. For more details see slide 15 in the slide deck distributed with the ExLogAnalyzer (ExLogAnalyzer.ppt).
@aschnelk - I'm glad you like the functionality and performance of the tool. Note that the performance is affected by the analyzers you run. The ones that re-write all of the logs (e.g. smtp sessions one) will be the ones that will add the most time to your run.
@Trix - LogParser works well for certain kinds of queries against relatively well structured logs. However, ExLogAnalyzer will provide you with more flexibility in processing behavior over time, supporting concepts like sessions, having state machines in your analyzers and analyzing logs like smtp receive, which would be much harder to analyze using LogParser. I believe there are benefits to both tools. Would like to hear your feedback once you try out the prepackaged analyzers.
@everyone, thanks for the feedback. Please keep positing your opinions, ideas, usage experience and feature requests too.