Linux workstation

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
Metadata completeness
70/100 (not a software quality rating)
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. liblognorm

    Alpine Linux 3.21 / source liblognorm

    2.0.6-r5

    A fast log-normalization library

    aarch64x86_64v3.21
  2. liblognorm-dev

    Alpine Linux 3.21 / source liblognorm

    2.0.6-r5

    A fast log-normalization library (development files)

    aarch64x86_64v3.21

Alpine Linux 3.22

  1. liblognorm

    Alpine Linux 3.22 / source liblognorm

    2.0.6-r5

    A fast log-normalization library

    aarch64x86_64v3.22
  2. liblognorm-dev

    Alpine Linux 3.22 / source liblognorm

    2.0.6-r5

    A fast log-normalization library (development files)

    aarch64x86_64v3.22

Alpine Linux 3.23

  1. liblognorm

    Alpine Linux 3.23 / source liblognorm

    2.0.6-r5

    A fast log-normalization library

    aarch64x86_64v3.23
  2. liblognorm-dev

    Alpine Linux 3.23 / source liblognorm

    2.0.6-r5

    A fast log-normalization library (development files)

    aarch64x86_64v3.23

Debian 12 (Bookworm)

  1. liblognorm5

    Debian 12 (Bookworm) / libs / source liblognorm

    2.0.6-4

    log normalizing library

    amd64arm64bookworm
  2. liblognorm-dev

    Debian 12 (Bookworm) / libdevel / source liblognorm

    2.0.6-4

    log normalizing library - development files

    amd64arm64bookworm
  3. liblognorm-doc

    Debian 12 (Bookworm) / doc / source liblognorm

    2.0.6-4

    log normalizing library - developer documentation

    allbookworm
  4. liblognorm-utils

    Debian 12 (Bookworm) / admin / source liblognorm

    2.0.6-4

    log normalizing utilities

    amd64arm64bookworm

Debian 13 (Trixie)

  1. liblognorm5

    Debian 13 (Trixie) / libs / source liblognorm

    2.0.6-5

    log normalizing library

    amd64arm64trixie
  2. liblognorm-dev

    Debian 13 (Trixie) / libdevel / source liblognorm

    2.0.6-5

    log normalizing library - development files

    amd64arm64trixie
  3. liblognorm-doc

    Debian 13 (Trixie) / doc / source liblognorm

    2.0.6-5

    log normalizing library - developer documentation

    alltrixie
  4. liblognorm-utils

    Debian 13 (Trixie) / admin / source liblognorm

    2.0.6-5

    log normalizing utilities

    amd64arm64trixie

openSUSE Leap 16.0

  1. liblognorm5

    openSUSE Leap 16.0 / Development/Libraries/C and C++ / source liblognorm

    2.0.6-160000.2.2

    Library and tool to normalize log data

    aarch64ppc64les390xx86_64leap-16.0
  2. liblognorm-devel

    openSUSE Leap 16.0 / Development/Libraries/C and C++ / source liblognorm

    2.0.6-160000.2.2

    Development files for liblognorm

    aarch64ppc64les390xx86_64leap-16.0

openSUSE Tumbleweed

  1. liblognorm5

    openSUSE Tumbleweed / Development/Libraries/C and C++ / source liblognorm

    2.1.0-1.3

    Library and tool to normalize log data

    x86_64tumbleweed
  2. liblognorm-devel

    openSUSE Tumbleweed / Development/Libraries/C and C++ / source liblognorm

    2.1.0-1.3

    Development files for liblognorm

    x86_64tumbleweed

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.