Parents (Total: 5)

The searched file hash is included in 5 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	A2D741AF0F9A8A9C0B51D5481D8BEDBF
PackageArch	x86_64
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	liblognorm-devel
PackageRelease	lp150.1.3
PackageVersion	2.0.4
SHA-1	79EEC9C79B1B6BDC64480820C5AC5881CED7F224
SHA-256	451296413F2062297990F7366FA5096ACB5DA41CDE2B4942C7D197108E6065D1

Key	Value
MD5	E62385C8EE001728884E7EFAC06B3BCE
PackageArch	x86_64
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	liblognorm-devel
PackageRelease	lp152.3.6
PackageVersion	2.0.4
SHA-1	B7206FDA0A93A25331E92E1651500C49ADB8AC27
SHA-256	5C40ED664C7006FD63DD4245F66B6D8219867856CC7ED3752B3434FCF97B0721

Key	Value
MD5	EBD28FB3BC5E40A47CA4A284E44AF3DB
PackageArch	x86_64
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	liblognorm-devel
PackageRelease	lp151.2.3
PackageVersion	2.0.4
SHA-1	B2FCA2B4C9E0B89932C778C016D1E7A08D6EDC18
SHA-256	0BC42E742716E6C16D866086736BD1E9338B77EB75E7BAB41D898E448C938EFF

Key	Value
MD5	74098A976FA0407EF142F1F627C62B95
PackageArch	x86_64
PackageDescription	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.
PackageMaintainer	https://www.suse.com/
PackageName	liblognorm-devel
PackageRelease	1.17
PackageVersion	2.0.4
SHA-1	44799B372E923602D75A7083AB8270DC91A1338F
SHA-256	17C405252D9BB6A7A29156B1C5C3B29DE7CC93A5E1A2C738F203536A59B9386B

Key	Value
MD5	C48E8EA98D96112E2F4A95697D5C683B
PackageArch	s390x
PackageDescription	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.
PackageMaintainer	https://www.suse.com/
PackageName	liblognorm-devel
PackageRelease	1.17
PackageVersion	2.0.4
SHA-1	1FA0494EADD7130041253E5FB63068A970B33DE4
SHA-256	FBA102AF59D5011A25F9FFB1954FC65B6234D277D7335EB6CE1561709BC804E7