[logback-dev] log file parser requierements

[Johannes Bühler]

Hi Tony,
looks like you layed a good ground for continue working with. So far I do not yet have any concrete thoughts in mind how the decoder will finally look like, so I will try to continue what you already achieved. Thanks for the good test coverage, that will help me a lot to get started.  

Johannes



On Tuesday, April 23, 2013 at 2:31 AM, Tony Trinh wrote:

> Hi Johannes,
>  
> Thanks for jumping in. :-)  I'm open to design-changes you might have in mind (including refactoring some/all components).
>  
> Tony  
>  
>  
> On Mon, Apr 22, 2013 at 4:33 PM, ceki <ceki at qos.ch (mailto:ceki at qos.ch)> wrote:
> > Tony Trinh has done quite a bit of work on logback-decoder. The
> > exchange in [1] is probably worth reading.
> >  
> > Given a pattern, the core idea is to create regular expressions from
> > that pattern. Once we have the regular expression containing grouping
> > instructions, we can capture various ILoggingeEvent fields.
> >  
> > Tony has written several classes under the
> > ch.qos.logback.decoder.regex package for this purpose.
> >  
> > Assuming each log line corresponds to a ILoggingEvent, once we have
> > the correct regular expression, we can go through the file and convert
> > each line into an ILoggingEvent.
> >  
> > I think it is easier to start by solving this sub-problem before
> > trying to convert events spanning multiple lines.
> >  
> > We can also ignore AccessEvent conversions (events generated by
> > logback-access) in the initial stages of the project.
> >  
> > [1] http://markmail.org/message/wqqaxztmjqfuklri
> >  
> >  
> > On 22.04.2013 23:04, Johannes Bühler wrote:
> > > Hi Ceki,
> > > Sounds good to me to get started.
> > >  
> > > Thanks,
> > > Johannes
> > >  
> > > On Monday, April 22, 2013 at 10:49 PM, ceki wrote:
> > >  
> > > >  
> > > > Hi Johannes,
> > > >  
> > > > Cool.
> > > >  
> > > > The goal of logback-decoder is to convert one or more lines found in a
> > > > log file (containing text) into a series of objects of type
> > > > ILoggingEvent. Thus, FileAppender converts instances of ILoggingEvent
> > > > into one or more lines in a log file, a decoder performs the inverse
> > > > operation.
> > > >  
> > > > It should be assumed that the first line of the log file contains the
> > > > pattern that was used to format the output. See
> > > > http://logback.qos.ch/manual/encoders.html#outputPatternAsHeader for
> > > > further details.
> > > >  
> > > > Is the above sufficient to get you started?
> > > >  
> > > > On 22.04.2013 22:27, Johannes Bühler wrote:
> > > > > Hi all,
> > > > > Ceki asked for a volunteer for writing a logback log file parser. I am
> > > > > interested in doing it.
> > > > > Are there already some initial requierements available?
> > > > > Looking forward to it!
> > > > >  
> > > > > Cheers,
> > > > > Johannes
> > > >  
> >  
> >  
> > --  
> > Ceki
> > 65% of statistics are made up on the spot
> > _______________________________________________
> > logback-dev mailing list
> > logback-dev at qos.ch (mailto:logback-dev at qos.ch)
> > http://mailman.qos.ch/mailman/listinfo/logback-dev
>  
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch (mailto:logback-dev at qos.ch)
> http://mailman.qos.ch/mailman/listinfo/logback-dev
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20130423/88299c3a/attachment-0001.html>