Parents (Total: 82)

The searched file hash is included in 82 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	DAE1A680735CD4712BBE7D185A8837E3
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.
PackageName	liblognorm5
PackageRelease	150400.51.1
PackageVersion	2.0.6
SHA-1	072109A9280C7C5C946034F3E07895919CB2A8AE
SHA-256	C96C1C8D7495022103A426A728071E1C6E987AB5159CE8C1A88EDF0E0B833055

Key	Value
MD5	61051D1A0B75F2E046520A2F49417FD4
PackageArch	x86_64
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	9.fc32
PackageVersion	2.0.3
SHA-1	07260EA14C2BAC05EA84CC6083E21264CC28E36F
SHA-256	4AC6A08305928AAD8D608648168F4B541418FF84D39A78AFC9D3916C4A988EC8

Key	Value
MD5	99FC390EEE33D77DB33ED746F98F0156
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.
PackageName	liblognorm5
PackageRelease	51.6
PackageVersion	2.0.6
SHA-1	08E2A7BDDCEB982C8DC4EA49B017CDC2B2FA7DE5
SHA-256	FB1DC2B0F55DE1BB8073E14155C34A4EBEE7BDBF1C75835FF6AB9A4112086D8A

Key	Value
MD5	47CF57E64F56A4DDA998B26FE84CFA2F
PackageArch	ppc64le
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	CentOS Buildsys <bugs@centos.org>
PackageName	liblognorm
PackageRelease	2.el8
PackageVersion	2.0.5
SHA-1	092FE78B70164C739505C1CB6AE6FFF7C5309F1E
SHA-256	47808C3A968288565FB71FD60098F8A878FAF136BE14291D8CE8056086720522

Key	Value
MD5	DFE3990467015998F2A5CC64548C1C7F
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.
PackageName	liblognorm5
PackageRelease	51.58
PackageVersion	2.0.6
SHA-1	0B0DF91F39C54B25CD990069B71A664AD63CDCC8
SHA-256	53C5095A9EB98D8EB2EA8B926CFDE3153BB2214AB617C18E8A6537A53382A09F

Key	Value
MD5	A7B075C4D4BF8C5491D8E48716CCE95B
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.
PackageName	liblognorm5
PackageRelease	51.58
PackageVersion	2.0.6
SHA-1	0D8F02D0D50C0B3DFC562BFCA585E2E3734411AD
SHA-256	F8D0540D0E52FC31407C08DEA8A3BA54954E4A2A36E2972A1C7AFC98517B383F

Key	Value
MD5	0CAAB3DF0296C22E64300FDF6AC1BC11
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	9.fc32
PackageVersion	2.0.3
SHA-1	0FBFFF4E73059D782C33BEC03A0EDD1B97F231B1
SHA-256	F35E45140049C1017EF527560335A6C574937BB97BC937FD23E8EA3882F84CD8

Key	Value
MD5	A70161C9EBDACE8506504CA325C05169
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.
PackageName	liblognorm5
PackageRelease	lp153.51.10
PackageVersion	2.0.6
SHA-1	1065AC38CFBEC1089CF468132785679F01913003
SHA-256	5DCF3BE7E49227CC7318E0589B33BFF74C8760E6DAAD80B40EAEAE279EBE69BC