How to Install and Uninstall liblognorm5 Package on openSuSE Tumbleweed

Last updated: May 17,2024

1. Install "liblognorm5" package

Please follow the step by step instructions below to install liblognorm5 on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                liblognorm5
            
                    
    
    Copied

2. Uninstall "liblognorm5" package

Learn how to uninstall liblognorm5 on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                liblognorm5
            
                    
    
    Copied

3. Information about the liblognorm5 package on openSuSE Tumbleweed

Information for package liblognorm5:
------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : liblognorm5
Version : 2.0.6-2.21
Arch : x86_64
Vendor : openSUSE
Installed Size : 203.3 KiB
Installed : No
Status : not installed
Source package : liblognorm-2.0.6-2.21.src
Upstream URL : http://www.liblognorm.com/
Summary : Library and tool to normalize log data
Description :
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.