Upstream software project

liblognorm

A fast log-normalization library (development files)

About liblognorm

A fast log-normalization library (development files)

This project links 18 native package records across 7 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Alpine Linux 3.21: 2 package records; Alpine Linux 3.22: 2 package records; Alpine Linux 3.23: 2 package records; Debian 12 (Bookworm): 4 package records; Debian 13 (Trixie): 4 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.liblognorm: recorded package coverageAlpine Linux 3.212 recordsAlpine Linux 3.222 recordsAlpine Linux 3.232 recordsDebian 12 (Bookworm)4 recordsDebian 13 (Trixie)4 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
liblognorm
Publisher
Not authoritatively mapped
Native package records
18
Operating systems
alpine-linux-3-21, alpine-linux-3-22, alpine-linux-3-23, debian-12, debian-13, opensuse-leap-16-0, opensuse-tumbleweed
License expression
LGPL-2.1-or-later AND Apache-2.0
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Liblognorm is a library and a tool to normalize log data. Liblognorm shall help to make sense out of syslog data, or, actually, any event data that is present in text form. In short words, one will be able to throw arbitrary log message to liblognorm, one at a time, and for each message it will output well-defined name-value pairs and a set of tags describing the message. So, for example, if you have traffic logs from three different firewalls, liblognorm will be able to "normalize" the events into generic ones. Among others, it will extract source and destination ip addresses and ports and make them available via well-defined fields. As the end result, a common log analysis application will be able to work on that common set and so this backend will be independent from the actual firewalls feeding it. Even better, once we have a well-understood interim format, it is also easy to convert that into any other vendor specific format, so that you can use that vendor's analysis tool. The liblognorm-devel package contains libraries and header files for developing applications that use liblognorm.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Alpine Linux 3.21

  1. Package liblognorm

    v3.21 (Alpine Linux 3.21): A fast log-normalization library

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

  2. Package liblognorm-dev

    v3.21 (Alpine Linux 3.21): A fast log-normalization library (development files)

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

Alpine Linux 3.22

  1. Package liblognorm

    v3.22 (Alpine Linux 3.22): A fast log-normalization library

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

  2. Package liblognorm-dev

    v3.22 (Alpine Linux 3.22): A fast log-normalization library (development files)

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

Alpine Linux 3.23

  1. Package liblognorm

    v3.23 (Alpine Linux 3.23): A fast log-normalization library

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

  2. Package liblognorm-dev

    v3.23 (Alpine Linux 3.23): A fast log-normalization library (development files)

    2.0.6-r5: aarch64 x86_64

    Source: liblognorm

Debian 12 (Bookworm)

  1. Package liblognorm5

    bookworm (Debian 12 (Bookworm)) (libs): log normalizing library

    2.0.6-4: amd64 arm64

    Source: liblognorm

  2. Package liblognorm-dev

    bookworm (Debian 12 (Bookworm)) (libdevel): log normalizing library - development files

    2.0.6-4: amd64 arm64

    Source: liblognorm

  3. Package liblognorm-doc

    bookworm (Debian 12 (Bookworm)) (doc): log normalizing library - developer documentation

    2.0.6-4: all

    Source: liblognorm

  4. Package liblognorm-utils

    bookworm (Debian 12 (Bookworm)) (admin): log normalizing utilities

    2.0.6-4: amd64 arm64

    Source: liblognorm

Debian 13 (Trixie)

  1. Package liblognorm5

    trixie (Debian 13 (Trixie)) (libs): log normalizing library

    2.0.6-5: amd64 arm64

    Source: liblognorm

  2. Package liblognorm-dev

    trixie (Debian 13 (Trixie)) (libdevel): log normalizing library - development files

    2.0.6-5: amd64 arm64

    Source: liblognorm

  3. Package liblognorm-doc

    trixie (Debian 13 (Trixie)) (doc): log normalizing library - developer documentation

    2.0.6-5: all

    Source: liblognorm

  4. Package liblognorm-utils

    trixie (Debian 13 (Trixie)) (admin): log normalizing utilities

    2.0.6-5: amd64 arm64

    Source: liblognorm

openSUSE Leap 16.0

  1. Package liblognorm5

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/C and C++): Library and tool to normalize log data

    2.0.6-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: liblognorm

  2. Package liblognorm-devel

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/C and C++): Development files for liblognorm

    2.0.6-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: liblognorm

openSUSE Tumbleweed

  1. Package liblognorm5

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/C and C++): Library and tool to normalize log data

    2.1.0-1.3: x86_64

    Source: liblognorm

  2. Package liblognorm-devel

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/C and C++): Development files for liblognorm

    2.1.0-1.3: x86_64

    Source: liblognorm

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.