> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Champ Clark III [Softwink] > Sent: Friday, October 08, 2010 2:55 PM > To: [email protected] > Subject: [rsyslog] liblognorm > > > On Thu, Oct 07, 2010 at 05:26:18PM +0200, Rainer Gerhards wrote: > > Hi folks, > > > > I am happy to finally announce the liblognorm project, a facility to > > normalize all kinds of log messages. My initial announcement is here: > > > > http://blog.gerhards.net/2010/10/introducing-liblognorm.html > > > > I'd appreciate if you follow this effort and share the news. I plan > to do a > > couple of more blog posts within the next days. > > Very cool idea, and the strange thing is.... I was look, > yesterday, for the exact same idea of a library. Needless to say, > I found no such project. I have a couple of questions: > > What license do you plan on distributing liblognorm under?
It's not my sole decision, but I think it will most probably by LGPL v2 or v3. BSD may make some sense as we try to get it into wide-spread use, but I may not get along with this. My bet is that LGPL v2 will be the compromise. > The example formating (in your blog post) looks just about exactly what > I was thinking. :-) Starting this morning I have begun to wade in-depth through a pile of CEE docs (the upcoming standard). We may need to make some format adjustments, but I'd like to stick with somewhat as simple as possible to write for the samples. > Will the log formats, that is, what to look for, > be in a seperate text file that can be updated? As you mention in the > blog post, "much like a virus scanner". Actually, at this point nothing is really finalized. For the initial effort, it will definitely be a text file. But in the long term I can also envision that we should be able to pull it e.g. from web servers or load multiple files, or... actually something that should be configurable. > If that is the case, will programs that use liblognorm pull that into > an array first, and let liblognorm do it's work? Or will this file > have to be repeatedly referenced? In the long term I think it makes sense to provide a way to stuff samples in via either a dedicated API OR (and?) have them loaded based on a config file. The latter is what I have on my mind for the first step. > I'd love to help out in this, be it code wise and/or log examples. Any help is deeply appreciated and these questions already help! Log samples and trying out the library, once it materializes, would be a very very great aid. I will write a couple of more blog posts with more details, and everything is really open for change now. It would also be very useful if you could spread the news. An as wide audience as possible would be very good. Rainer > Thans for rsyslog, and keep up the great work. > > -- > Champ Clark III | Softwink, Inc | 800-538-9357 x 101 > http://www.softwink.com > > GPG Key ID: 58A2A58F > Key fingerprint = 7734 2A1C 007D 581E BDF7 6AD5 0F1F 655F 58A2 A58F > If it wasn't for C, we'd be using BASI, PASAL and OBOL. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
