• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

compat/H03-May-2022-731591

doc/H03-May-2022-2,6361,804

m4/H06-Nov-2018-9,0758,203

rulebases/H03-May-2022-9270

src/H03-May-2022-16,13611,058

tests/H03-May-2022-6,2994,407

tools/H03-May-2022-521407

AUTHORSH A D04-May-201854 21

COPYINGH A D04-May-201825.4 KiB491409

COPYING.ASL20H A D04-May-20188.9 KiB5127

ChangeLogH A D06-Nov-201813.6 KiB265264

INSTALLH A D06-Nov-201815.4 KiB369287

Makefile.amH A D04-May-2018244 1612

Makefile.inH A D03-May-202227.9 KiB894794

NEWSH A D04-May-201863 21

READMEH A D04-May-20182 KiB4030

aclocal.m4H A D06-Nov-201888.7 KiB2,3632,167

compileH A D06-Nov-20187.2 KiB348258

config.guessH A D06-Nov-201843.2 KiB1,4811,288

config.h.inH A D06-Nov-20183.7 KiB149105

config.subH A D06-Nov-201835.3 KiB1,8021,661

configureH A D06-Nov-2018510.4 KiB17,65914,661

configure.acH A D06-Nov-20186.1 KiB199175

depcompH A D06-Nov-201823 KiB792502

install-shH A D06-Nov-201814.8 KiB509329

lognorm.pc.inH A D04-May-2018288 1311

ltmain.shH A D06-Nov-2018316.8 KiB11,1577,986

missingH A D06-Nov-20186.7 KiB216143

test-driverH A D06-Nov-20184.5 KiB14987

README

1Liblognorm is a fast-samples based normalization library.
2
3More information on liblognorm can be found at
4    http://www.liblognorm.com
5
6Liblognorm evolves since several years and was intially meant to be used primarily with
7the Mitre CEE effort. Consequently, the initial version of liblognorm (0.x)
8uses the libee CEE support library in its API.
9
10As time evolved, the initial CEE schema underwent considerable change. Even
11worse, Mitre lost funding for CEE. While the CEE ideas survived as part
12of Red Hat-driven "Project Lumberjack", the data structures became greatly
13simplified and JSON based. That effectively made libee obsolete (and also
14in parts libestr, which was specifically written to support CEE's
15initial requirement of embedded NUL chars in strings).
16
17In 2013, Pavel Levshin converted liblognorm to native JSON, which helped
18improve performance and simplicity for many client applications.
19Unfortunately, this change broke interface compatibility (and there was
20no way to avoid that, obviously...).
21
22In 2015, most parts of liblognorm were redesigned and rewritten as part
23of Rainer Gerhards' master thesis. For full technical details of how
24liblognorm operates, and why it is so fast, please have a look at
25
26https://www.researchgate.net/publication/310545144_Efficient_Normalization_of_IT_Log_Messages_under_Realtime_Conditions
27
28The current library is the result of that effort. Application developers
29are encouraged to switch to this version, as it provides the benefit of
30a simpler API. This version is now being tracked by the git master branch.
31
32However, if you need to stick to the old API, there is a git branch
33liblognorm0, which contains the previous version of the library. This
34branch is also maintained for important bug fixes, so it is safe to use.
35
36We recommend that packagers create packages both for liblognorm0 and
37liblognorm1. Note that liblognorm's development packages cannot
38coexist on the same system as the PKGCONFIG system would get into
39trouble. Adiscon's own packages follow this schema.
40