Parents (Total: 21)

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

Key	Value
MD5	E257D5E737A7F551114640F815E777D7
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.
PackageName	liblognorm-devel
PackageRelease	51.58
PackageVersion	2.0.6
SHA-1	005D34FB5A36732A2D0BF7B86230DF029F3CA2B7
SHA-256	040BE856C18A17C958A75DCDBF81DF64899F1B9A202464B7C4FF5C722526889D

Key	Value
MD5	AA72CD100B5463E4577BF4633743BA6D
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.
PackageName	liblognorm-devel
PackageRelease	lp153.51.10
PackageVersion	2.0.6
SHA-1	060AFFAE732EEA8C6B71851AE38BF56693FA29E7
SHA-256	672ECE527F9784F412E18DD2191086A105B152B59B57C28E5DBA0B55A2020F0B

Key	Value
MD5	25EFABE04C10B757728A99E19B7B7B17
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.
PackageName	liblognorm-devel
PackageRelease	lp154.51.1
PackageVersion	2.0.6
SHA-1	10A55737FF0D2117D2976FED48C0C0519916BF4F
SHA-256	8BA99FD2779EB4AD7463E68D3A979EB9B98AD8D77AC6872D122A4C08A3E894B8

Key	Value
MD5	E946267D873098CC4373562CFF6B429B
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	150000.3.3.1
PackageVersion	2.0.6
SHA-1	1693C336C7BB0FF54DE677FA87E9DBECB32BFF12
SHA-256	DC6BBD02CB3EA4519A287843CB75AD54B77C3EB387189D45C69FFAAFC00DAC19

Key	Value
MD5	5698FC5129F7EC543EBB8B6837799C8E
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.
PackageName	liblognorm-devel
PackageRelease	51.1
PackageVersion	2.0.6
SHA-1	2B4BC582DA7FE78F29F69BCD2F99466F9FD35382
SHA-256	5D703074796CB58124E061003EC0F0762757E898E20F3DC868CEAA929971AD85

Key	Value
MD5	1BDB7E9721F848E22A0B72732D6B54A1
PackageArch	armv7hl
PackageDescription	Briefly described, liblognorm is a tool to normalize log data. People who need to take a look at logs often have a common problem. Logs from different machines (from different vendors) usually have different formats for their logs. Even if it is the same type of log (e.g. from firewalls), the log entries are so different, that it is pretty hard to read these. This is where liblognorm comes into the game. With this tool you can normalize all your logs. All you need is liblognorm and its dependencies and a sample database that fits the logs you want to normalize.
PackageMaintainer	Fedora Project
PackageName	liblognorm
PackageRelease	1.fc34
PackageVersion	2.0.6
SHA-1	300E55A4956BCF625E9D417E226DCB879885F8F0
SHA-256	D49CC30D7481CA9491CF044688A7582CAB0722A20EADE927A4CCBD7197C8FA61

Key	Value
MD5	0F5E85F51DA0834B26654450078CE10D
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.
PackageName	liblognorm-devel
PackageRelease	lp151.51.1
PackageVersion	2.0.6
SHA-1	4E5E07666FFAACF227AEB690E581F6D9A5F09D72
SHA-256	FC19EB7B03C3E8B56FE8F1CFC754E0E241BF28B53B8534A7A9D30F30B4774F4E

Key	Value
MD5	405C53B87BBA36A22156514A99246EE0
PackageArch	armv7hl
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.
PackageName	liblognorm-devel
PackageRelease	51.38
PackageVersion	2.0.6
SHA-1	4FF9CB2D2F904D722EC229E7D7CA03F367EB11F3
SHA-256	23FA442C540A51BEA245DC3697BF86282C25F964F6574D30C8F744D1953199CE

Key	Value
MD5	162FC200E06902AE5E2AD30167C639F1
PackageArch	i686
PackageDescription	Briefly described, liblognorm is a tool to normalize log data. People who need to take a look at logs often have a common problem. Logs from different machines (from different vendors) usually have different formats for their logs. Even if it is the same type of log (e.g. from firewalls), the log entries are so different, that it is pretty hard to read these. This is where liblognorm comes into the game. With this tool you can normalize all your logs. All you need is liblognorm and its dependencies and a sample database that fits the logs you want to normalize.
PackageMaintainer	Fedora Project
PackageName	liblognorm
PackageRelease	1.fc34
PackageVersion	2.0.6
SHA-1	69338C3F83AF405D3451CCA63BF79BA0F3DFDF30
SHA-256	BF41E9DF4C7A8D0D5E78A72318B53D6073FAA7EA2DE5A8DEB939B7495C68854D

Key	Value
MD5	2A639C2FE1A9331DB242BC684DC892C4
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.
PackageName	liblognorm-devel
PackageRelease	51.4
PackageVersion	2.0.6
SHA-1	6C7DF99D2253C618F335762C687544D30A94864B
SHA-256	580755FB12711319AB38C525B826B20B8FBEAD00E990D088F0754ACE6CB708D9