From 0443ca353f0ea009a543fc71d241f133ba59c98b Mon Sep 17 00:00:00 2001 From: Baubak Gandomi Date: Tue, 23 Aug 2022 15:12:15 +0200 Subject: [PATCH 01/25] Fixed Update the documentation regarding installation. Also added code example --- README.md | 112 +++++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 85 insertions(+), 27 deletions(-) diff --git a/README.md b/README.md index 91455ab..c175471 100644 --- a/README.md +++ b/README.md @@ -12,10 +12,13 @@ The basic method for using this library is, that you create a definition for you # Table of contents +- [Installation](#installation) + - [Maven](#maven) - [Parse Definitions](#parse-definitions) - [Defining a Parsing](#defining-a-parsing) - [Defining an entry](#defining-an-entry) - [How parsing works](#how-parsing-works) + - [Code Example](#code-example) - [Import and Export](#import-and-export) - [Using the Standard Method](#using-the-standard-method) - [Using the SDK](#using-the-sdk) @@ -26,6 +29,20 @@ The basic method for using this library is, that you create a definition for you - [Assertions and LogDataAssertions](#assertions-and-logdataassertions) - [Release Notes](#release-notes) +## Installation +For now we are using this library with maven, in later iteration we will publish other build system examples: + +### Maven +The following dependency needs to be added to your pom file: + +``` + + com.adobe.campaign.tests + log-parser + 1.0.8 + +``` + ## Parse Definitions In order to parse logs you need to define a ParseDefinition. A ParseDefinition contains a set of ordered ParseDefinition Entries. While parsing a line of logs, the LogParser will see if all entries can be found in the line of logs. If that is the case, the line is stored according to the definitions. @@ -53,6 +70,46 @@ By using the StringParseFactory we get a LogData object with allows us to manage ![Parsing a log line](diagrams/Log_Parser-log-parsing.png) +### Code Example +Here is an example of how we can parse a string. The method is leveraged to perform the same parsing in one or many files. + +```java +@Test +public void parseAStringDemo() throws StringParseException { + String logString = "afthostXX.qa.campaign.adobe.com:443 - - [02/Apr/2022:08:08:28 +0200] \"GET /rest/head/workflow/WKF193 HTTP/1.1\" 200 "; + + //Create a parse definition + ParseDefinitionEntry verbDefinition = new ParseDefinitionEntry(); + verbDefinition.setTitle("verb"); + verbDefinition.setStart("\""); + verbDefinition.setEnd(" /"); + + ParseDefinitionEntry apiDefinition = new ParseDefinitionEntry(); + apiDefinition.setTitle("path"); + apiDefinition.setStart(" /"); + apiDefinition.setEnd(" "); + + List definitionList = Arrays.asList(verbDefinition,apiDefinition); + + //Perform Parsing + Map parseResult = StringParseFactory.parseString(logString, definitionList); + + //Check Results + assertThat("We should have an entry for verb", parseResult.containsKey("verb")); + assertThat("We should have the correct value for logDate", parseResult.get("verb"), is(equalTo("GET"))); + + assertThat("We should have an entry for the API", parseResult.containsKey("path")); + assertThat("We should have the correct value for logDate", parseResult.get("path"), + is(equalTo("rest/head/workflow/WKF193"))); +} +``` +In the code above we want to parse the log line below, and want to fin the REST call "GET /rest/head/workflow/WKF193", and to extract the verb "GET", and the api "/rest/head/workflow/WKF193". +`afthostXX.qa.campaign.adobe.com:443 - - [02/Apr/2022:08:08:28 +0200] \"GET /rest/head/workflow/WKF193 HTTP/1.1\" 200` + +The code starts with the creation a parse definition with at least two parse definitions that tell us between which markers should each data be extracted. The parse difinition is then handed to the StringParseFactory so that the data can be extracted. +At the end we can see that each data is stored in a map with the parse defnition entry title as a key. + + ### Import and Export You can import or store a Parse Definition to or from a JSON file. @@ -172,30 +229,31 @@ AssertLogData.assertLogContains(List in_filePathList, ParseDefinition in `AssertLogData.assertLogContains(List, ParseDefinition, String, String)` allows you to perform an assertion directly on a file. ## Release Notes -- 1.0.7 - - #39 updated the log4J library to 2.17.1 to avoid the PSIRT vulnerability -- 1.0.6 - - #38 Resolved some issues with HashCode - - #37 Upgraded the build to Java11 - - #34 Activated sonar in the build process -- 1.0.5 - - #23 Added the searchEntries, and the isEntryPresent methods. - - #20 Adding log data assertions - - keyOrder is now a List - - #32 we have solved an issue with exporting and importing the key orders - - #30 Allowing for the LogDataFactory to accept a JSON file as input for the ParseDefinitions - - #31 Solved bug with importing the JSON file -- 1.0.4 - - #6 We Can now import a definition from a JSON file. You can also export a ParseDefinition into a JSON file. - - #8 & #18 Added the filter function. - - #13 Added copy constructors. - - #13 Added a copy method in the StdLogEntry (#13). - - #14 Added a set method to LogData. This allows you to change a Log data given a key value and ParseDefinition entry title - - Renamed exception IncorrectParseDefinitionTitleException to IncorrectParseDefinitionException. - - -- 1.0.3 - - Introduced the LogData Top Class. This encapsulates all results. - - Introduced the LogDataFactory - - Added the groupBy method to extract data from the results -- 1.0.1 - - Open source release. +### 1.0.8 +- Moving back to Java 8 as our clients are still using Java8 +### 1.0.7 +- #39 updated the log4J library to 2.17.1 to avoid the PSIRT vulnerability +### 1.0.6 +- #38 Resolved some issues with HashCode +- #37 Upgraded the build to Java11 +- #34 Activated sonar in the build process +### 1.0.5 +- #23 Added the searchEntries, and the isEntryPresent methods. +- #20 Adding log data assertions +- keyOrder is now a List +- #32 we have solved an issue with exporting and importing the key orders +- #30 Allowing for the LogDataFactory to accept a JSON file as input for the ParseDefinitions +- #31 Solved bug with importing the JSON file +### 1.0.4 +- #6 We Can now import a definition from a JSON file. You can also export a ParseDefinition into a JSON file. +- #8 & #18 Added the filter function. +- #13 Added copy constructors. +- #13 Added a copy method in the StdLogEntry (#13). +- #14 Added a set method to LogData. This allows you to change a Log data given a key value and ParseDefinition entry title +- Renamed exception IncorrectParseDefinitionTitleException to IncorrectParseDefinitionException. +### 1.0.3 +- Introduced the LogData Top Class. This encapsulates all results. +- Introduced the LogDataFactory +- Added the groupBy method to extract data from the results +### 1.0.1 +- Open source release. \ No newline at end of file From d5d2fa05756673169f825cb399f0828cb76c8a4d Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Wed, 31 Aug 2022 16:38:58 +0000 Subject: [PATCH 02/25] [maven-release-plugin] prepare release log-parser-1.0.8 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index d16da0d..da6b03f 100644 --- a/pom.xml +++ b/pom.xml @@ -17,7 +17,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.8-SNAPSHOT + 1.0.8 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -40,7 +40,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.0.8 From 36959f844a81850688ba9d0ed38b2f07d732c554 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Wed, 31 Aug 2022 16:39:00 +0000 Subject: [PATCH 03/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index da6b03f..d390de9 100644 --- a/pom.xml +++ b/pom.xml @@ -17,7 +17,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.8 + 1.0.9-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -40,7 +40,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.0.8 + HEAD From 9dd3d7688e61e746cc16c5ad4202d47d2c85e079 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 28 Oct 2022 14:12:51 +0000 Subject: [PATCH 04/25] [maven-release-plugin] prepare release log-parser-1.0.8.2 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 809df1e..57a93d8 100644 --- a/pom.xml +++ b/pom.xml @@ -17,7 +17,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.8.2-SNAPSHOT + 1.0.8.2 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -40,7 +40,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.0.8.2 From e230fb65b95ccbcf8893a40be514a397febef308 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 28 Oct 2022 14:12:52 +0000 Subject: [PATCH 05/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 57a93d8..81e413e 100644 --- a/pom.xml +++ b/pom.xml @@ -17,7 +17,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.8.2 + 1.0.8.3-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -40,7 +40,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.0.8.2 + HEAD From c1797fa249773717666d3db32483089b287e6c4c Mon Sep 17 00:00:00 2001 From: baubakg Date: Fri, 28 Oct 2022 16:16:24 +0200 Subject: [PATCH 06/25] Moving back to 1.0.9-SNAPSHOT --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 81e413e..78d5a63 100644 --- a/pom.xml +++ b/pom.xml @@ -17,7 +17,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.8.3-SNAPSHOT + 1.0.9-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. From e637958e97f54be12f6c786a213767629baaffd4 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 28 May 2024 13:37:24 +0000 Subject: [PATCH 07/25] [maven-release-plugin] prepare release log-parser-1.0.9 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index b25784d..d0a2a75 100644 --- a/pom.xml +++ b/pom.xml @@ -19,7 +19,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.9-SNAPSHOT + 1.0.9 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -42,7 +42,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.0.9 From de09447e033bcd10ada1acb76da2e9b2fee4cc76 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 28 May 2024 13:37:25 +0000 Subject: [PATCH 08/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index d0a2a75..0e4db8c 100644 --- a/pom.xml +++ b/pom.xml @@ -19,7 +19,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.9 + 1.0.10-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -42,7 +42,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.0.9 + HEAD From 5bb23de68eec1940446ab8665b70aa5b7b982e95 Mon Sep 17 00:00:00 2001 From: baubakg Date: Tue, 28 May 2024 17:27:27 +0200 Subject: [PATCH 09/25] Fixing issue with javadoc --- .../adobe/campaign/tests/logparser/utils/CSVManager.java | 9 ++++----- .../adobe/campaign/tests/logparser/core/LogDataTest.java | 4 ++-- .../campaign/tests/logparser/utils/CSVManagerTest.java | 2 +- 3 files changed, 7 insertions(+), 8 deletions(-) diff --git a/src/main/java/com/adobe/campaign/tests/logparser/utils/CSVManager.java b/src/main/java/com/adobe/campaign/tests/logparser/utils/CSVManager.java index 5a4d8e3..f013e4e 100644 --- a/src/main/java/com/adobe/campaign/tests/logparser/utils/CSVManager.java +++ b/src/main/java/com/adobe/campaign/tests/logparser/utils/CSVManager.java @@ -20,7 +20,6 @@ import java.util.HashMap; import java.util.List; import java.util.Map; -import java.util.Set; import java.util.stream.Collectors; public class CSVManager { @@ -31,13 +30,13 @@ public class CSVManager { *

* Author : gandomi * - * @param in_fileToLoad - * @param in_key + * @param in_fileToLoad A file to fetch + * @param in_key The header key to use as the key in the map * @return A map with the key being the LogDataKey and the values stored for that LogEntry * @throws FileNotFoundException if the file is absent - * @throws IOException + * @throws IOException if the file cannot be read */ - public static Map> fetchCoverageHistoryData(final String in_key, + public static Map> fetchCSVToMapList(final String in_key, final File in_fileToLoad) throws FileNotFoundException, IOException { Map> l_coverageHistory = new HashMap>(); diff --git a/src/test/java/com/adobe/campaign/tests/logparser/core/LogDataTest.java b/src/test/java/com/adobe/campaign/tests/logparser/core/LogDataTest.java index a1d1a36..67a44a6 100644 --- a/src/test/java/com/adobe/campaign/tests/logparser/core/LogDataTest.java +++ b/src/test/java/com/adobe/campaign/tests/logparser/core/LogDataTest.java @@ -1368,7 +1368,7 @@ public void testExportData() assertThat("We successfully created the file correctly", l_exportedFile.getName(), Matchers.endsWith(l_fileNameToExpect + "-export.csv")); - Map> l_fetchedResult = CSVManager.fetchCoverageHistoryData(StdLogEntry.STD_DATA_KEY, + Map> l_fetchedResult = CSVManager.fetchCSVToMapList(StdLogEntry.STD_DATA_KEY, l_exportedFile); for (GenericEntry l_ge : l_logData.getEntries().values()) { @@ -1415,7 +1415,7 @@ public void testExportDataFileExists() assertThat("We successfully created the file correctly", l_exportedFile.getName(), Matchers.endsWith(l_fileNameToExpect)); - Map> l_fetchedResult = CSVManager.fetchCoverageHistoryData(StdLogEntry.STD_DATA_KEY, + Map> l_fetchedResult = CSVManager.fetchCSVToMapList(StdLogEntry.STD_DATA_KEY, l_exportedFile); for (GenericEntry l_ge : l_logData.getEntries().values()) { diff --git a/src/test/java/com/adobe/campaign/tests/logparser/utils/CSVManagerTest.java b/src/test/java/com/adobe/campaign/tests/logparser/utils/CSVManagerTest.java index 5d0ee31..afe4fb0 100644 --- a/src/test/java/com/adobe/campaign/tests/logparser/utils/CSVManagerTest.java +++ b/src/test/java/com/adobe/campaign/tests/logparser/utils/CSVManagerTest.java @@ -35,7 +35,7 @@ public void fetchCoverageHistoryData_noFile() throws IOException { final File l_csvFile = new File(faker.file().fileName()); Map> l_coverageHistory = csvManager - .fetchCoverageHistoryData(faker.name().firstName(), l_csvFile); + .fetchCSVToMapList(faker.name().firstName(), l_csvFile); assertThat("We should have an empty map", l_coverageHistory.isEmpty()); From 5e09c2437d6bbad8de3b73b0495437ff7fad7e8b Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 28 May 2024 15:32:11 +0000 Subject: [PATCH 10/25] [maven-release-plugin] prepare release log-parser-1.0.10 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 0e4db8c..4f90620 100644 --- a/pom.xml +++ b/pom.xml @@ -19,7 +19,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.10-SNAPSHOT + 1.0.10 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -42,7 +42,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.0.10 From 8f173e7b969e2c83ce1a9f6f6b4ad7053ec7e1a6 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 28 May 2024 15:32:12 +0000 Subject: [PATCH 11/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 4f90620..0a16261 100644 --- a/pom.xml +++ b/pom.xml @@ -19,7 +19,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.0.10 + 1.0.11-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -42,7 +42,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.0.10 + HEAD From 100d202ca11e81570e52edd9e36ed5e54fca1718 Mon Sep 17 00:00:00 2001 From: baubakg Date: Tue, 28 May 2024 17:52:33 +0200 Subject: [PATCH 12/25] Updating release notes --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 48fbc07..612df44 100644 --- a/README.md +++ b/README.md @@ -233,7 +233,7 @@ We now have the possibility to export the log data results into a CSV file. The ## Release Notes -### 1.0.9 +### 1.0.10 - Moved main code and tests to the package "core" - [#67](https://github.com/adobe/log-parser/issues/67) We can now select the files using a wild card. Given a directory we can now look for files in the sub-directory given a wild-card. The wildcards are implemented using Adobe Commons IO. You can read more on this in the [WildcardFilter JavaDoc](https://commons.apache.org/proper/commons-io/apidocs/org/apache/commons/io/filefilter/WildcardFilter.html) - [#68](https://github.com/adobe/log-parser/issues/68) We now present a report of the findings at the end of the analysis. From 97915e4a736ae5e7db5149681c1640e0c46b165b Mon Sep 17 00:00:00 2001 From: baubakg Date: Fri, 4 Oct 2024 11:53:40 +0200 Subject: [PATCH 13/25] finishing release notes --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 802d629..e5c80bf 100644 --- a/README.md +++ b/README.md @@ -471,7 +471,7 @@ You can get a print out of the command line options by running the command with All reports are stored in the directory `log-parser-reports/export/`. ## Changelog -### 1.11.0 (next version) +### 1.11.0 - **(new feature)** [#10](https://github.com/adobe/log-parser/issues/10) We now have an executable for the log-parser. You can perform a log parsing using the command line. For more information please read the section on [Command-line Execution of the Log-Parser](#command-line-execution-of-the-log-parser). - **(new feature)** [#127](https://github.com/adobe/log-parser/issues/127) You can now compare two LogData Objects. This is a light compare that checks that for a given key, if it is absent, added or changes in frequency. - **(new feature)** [#154](https://github.com/adobe/log-parser/issues/154) We have a data enrichment feature, where you can enrich the log data with additional information. For further details please refer to the section on [Enriching Log Data](#enriching-log-data). From 2ac754c916444445fd2285059eb103a0e61fd8ba Mon Sep 17 00:00:00 2001 From: baubakg Date: Fri, 4 Oct 2024 11:58:38 +0200 Subject: [PATCH 14/25] Fixing release notes --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e5c80bf..6d046c1 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,6 @@ The basic method for using this library is, that you create a definition for you ## Table of contents - * [Installation](#installation) * [Maven](#maven) * [Running the Log Parser](#running-the-log-parser) @@ -50,7 +49,7 @@ The basic method for using this library is, that you create a definition for you * [Exporting Results to an JSON File](#exporting-results-to-an-json-file) * [Command-line Execution of the Log-Parser](#command-line-execution-of-the-log-parser) * [Changelog](#changelog) - * [1.11.0 (next version)](#1110--next-version-) + * [1.11.0](#1110) * [1.0.10](#1010) * [1.0.8.2](#1082) * [1.0.8](#108) @@ -483,7 +482,7 @@ All reports are stored in the directory `log-parser-reports/export/`. - [#110](https://github.com/adobe/log-parser/issues/110) Moved to Java 11 - [#169](https://github.com/adobe/log-parser/issues/169) We only keep one Parse Definition entry with the same title in a Parse Definition. - [#157](https://github.com/adobe/log-parser/issues/157) Search terms ar no longer a Map of key and Objects. Instead, they are now a map of Parse Definition Entry names and Hamcrest Matchers. This may cause compilation errors for those using the search & filter functions. For migration purposes please refer to the section on [Defining a Search Term](#defining-a-search-term). -- [#57](https://github.com/adobe/log-parser/issues/57) Assertions are no longer an implicite assert equal method. We now allow Hamcrest Matchers for asserting. This can be one or more matchers. +- [#57](https://github.com/adobe/log-parser/issues/57) Assertions are no longer an implicit assert equal method. We now allow Hamcrest Matchers for asserting. This can be one or more matchers. - [#119](https://github.com/adobe/log-parser/issues/119) Cleanup of deprecated methods, and the consequences thereof. - [#137](https://github.com/adobe/log-parser/issues/137) We can now generate an HTML report for the differences in log data. - [#185](https://github.com/adobe/log-parser/issues/185) Resolved issue with deserializing unexpected objects in SDK Log entries.. From 852cf23b642a28513c0ed50d5c22495b0c154277 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 4 Oct 2024 10:00:34 +0000 Subject: [PATCH 15/25] [maven-release-plugin] prepare release log-parser-1.11.0 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 1fe0494..d145fa0 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.0-SNAPSHOT + 1.11.0 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.11.0 From f4a71b451795c4ddb95d696123944927585a2be3 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 4 Oct 2024 10:00:36 +0000 Subject: [PATCH 16/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index d145fa0..2c19764 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.0 + 1.11.1-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.11.0 + HEAD From 41c49d3a4e780a206c812813962cca364b3d3a59 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 4 Oct 2024 14:34:39 +0000 Subject: [PATCH 17/25] [maven-release-plugin] prepare release log-parser-1.11.1 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 2c19764..44a9a81 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.1-SNAPSHOT + 1.11.1 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.11.1 From 283a332ab241e2983077ea6823dd6ba0fae2987b Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Fri, 4 Oct 2024 14:34:40 +0000 Subject: [PATCH 18/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 44a9a81..32b5b8d 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.1 + 1.11.2-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.11.1 + HEAD From daedb0b23df29418dd9958d7617582ea8060f169 Mon Sep 17 00:00:00 2001 From: baubakg Date: Mon, 14 Oct 2024 11:11:23 +0200 Subject: [PATCH 19/25] Preparing release --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 99910d3..396009d 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ The following dependency needs to be added to your pom file: com.adobe.campaign.tests log-parser - 1.11.1 + 1.11.2 ``` ## Running the Log Parser From ef378f81004f1c72e6d74ca62013b4f9f2b2b0f9 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Mon, 14 Oct 2024 09:27:39 +0000 Subject: [PATCH 20/25] [maven-release-plugin] prepare release log-parser-1.11.2 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 32b5b8d..508c844 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.2-SNAPSHOT + 1.11.2 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.11.2 From 47d1fb3497fff9ee67b1965bd021080cdce169fc Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Mon, 14 Oct 2024 09:27:41 +0000 Subject: [PATCH 21/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 508c844..3ec3a35 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.2 + 1.11.3-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.11.2 + HEAD From f8f781a70ed51265b4dbfd3edfa7da60997e228a Mon Sep 17 00:00:00 2001 From: baubakg Date: Tue, 29 Apr 2025 18:59:39 +0200 Subject: [PATCH 22/25] Preparing for 1.11.3 --- README.md | 115 +++++++++++++++++++++++++++--------------------------- 1 file changed, 57 insertions(+), 58 deletions(-) diff --git a/README.md b/README.md index 880ae3e..4238c8a 100644 --- a/README.md +++ b/README.md @@ -14,62 +14,61 @@ The basic method for using this library is, that you create a definition for you ## Table of contents - -- [Installation](#installation) - - [Maven](#maven) -- [Running the Log Parser](#running-the-log-parser) -- [Parse Definitions](#parse-definitions) - - [Defining a Parsing](#defining-a-parsing) - - [Defining an Entry](#defining-an-entry) - - [How parsing works](#how-parsing-works) - - [Anonymizing Data](#anonymizing-data) - - [Code Example](#code-example) - - [Import and Export of Parse Definitions](#import-and-export-of-parse-definitions) - - [Importing a JSON File](#importing-a-json-file) -- [Extracting Data from Logs](#extracting-data-from-logs) - - [Using the Standard Method](#using-the-standard-method) - - [Using the Log-Parser as an SDK](#using-the-log-parser-as-an-sdk) - - [Writing your own SDK](#writing-your-own-sdk) - - [Declaring a Default and Copy Constructor](#declaring-a-default-and-copy-constructor) - - [Declaring the transformation Rules in setValuesFromMap](#declaring-the-transformation-rules-in-setvaluesfrommap) - - [Declaring the Key](#declaring-the-key) - - [Declare the HeaderMap, and ValueMap](#declare-the-headermap-and-valuemap) - - [Assisting Exports](#assisting-exports) -- [Code Structure](#code-structure) -- [Searching and organizing log data](#searching-and-organizing-log-data) - - [Search and Filter Mechanisms](#search-and-filter-mechanisms) - - [Defining a Search Term](#defining-a-search-term) - - [Enriching Log Data](#enriching-log-data) - - [GroupBy Mechanisms](#groupby-mechanisms) - - [Passing a list](#passing-a-list) - - [Chaining GroupBy](#chaining-groupby) - - [Comparing Log Data](#comparing-log-data) - - [Creating a Differentiation Report](#creating-a-differentiation-report) -- [Assertions and LogDataAssertions](#assertions-and-logdataassertions) -- [Exporting Parse Results](#exporting-parse-results) - - [Exporting Results to a CSV File](#exporting-results-to-a-csv-file) - - [Exporting Results to an HTML File](#exporting-results-to-an-html-file) - - [Exporting Results to an JSON File](#exporting-results-to-an-json-file) -- [Command-line Execution of the Log-Parser](#command-line-execution-of-the-log-parser) -- [Memory Guard Rails](#memory-guard-rails) - - [Guard Rail Properties](#guard-rail-properties) - - [File Entry Limitations](#file-entry-limitations) - - [File Size Limitations](#file-size-limitations) - - [Memory Limitations](#memory-limitations) - - [Exporting Anomalies Report](#exporting-anomalies-report) -- [Changelog](#changelog) -_ [1.11.3 (In-Progress)](#1113--in-progress-) -_ [1.11.2](#1112) -_ [1.11.0](#1110) -_ [1.0.10](#1010) -_ [1.0.8.2](#1082) -_ [1.0.8](#108) -_ [1.0.7](#107) -_ [1.0.6](#106) -_ [1.0.5](#105) -_ [1.0.4](#104) -_ [1.0.3](#103) -_ [1.0.1](#101) + * [Installation](#installation) + * [Maven](#maven) + * [Running the Log Parser](#running-the-log-parser) + * [Parse Definitions](#parse-definitions) + * [Defining a Parsing](#defining-a-parsing) + * [Defining an Entry](#defining-an-entry) + * [How parsing works](#how-parsing-works) + * [Anonymizing Data](#anonymizing-data) + * [Code Example](#code-example) + * [Import and Export of Parse Definitions](#import-and-export-of-parse-definitions) + * [Importing a JSON File](#importing-a-json-file) + * [Extracting Data from Logs](#extracting-data-from-logs) + * [Using the Standard Method](#using-the-standard-method) + * [Using the Log-Parser as an SDK](#using-the-log-parser-as-an-sdk) + * [Writing your own SDK](#writing-your-own-sdk) + * [Declaring a Default and Copy Constructor](#declaring-a-default-and-copy-constructor) + * [Declaring the transformation Rules in setValuesFromMap](#declaring-the-transformation-rules-in-setvaluesfrommap) + * [Declaring the Key](#declaring-the-key) + * [Declare the HeaderMap, and ValueMap](#declare-the-headermap-and-valuemap) + * [Assisting Exports](#assisting-exports) + * [Code Structure](#code-structure) + * [Searching and organizing log data](#searching-and-organizing-log-data) + * [Search and Filter Mechanisms](#search-and-filter-mechanisms) + * [Defining a Search Term](#defining-a-search-term) + * [Enriching Log Data](#enriching-log-data) + * [GroupBy Mechanisms](#groupby-mechanisms) + * [Passing a list](#passing-a-list) + * [Chaining GroupBy](#chaining-groupby) + * [Comparing Log Data](#comparing-log-data) + * [Creating a Differentiation Report](#creating-a-differentiation-report) + * [Assertions and LogDataAssertions](#assertions-and-logdataassertions) + * [Exporting Parse Results](#exporting-parse-results) + * [Exporting Results to a CSV File](#exporting-results-to-a-csv-file) + * [Exporting Results to an HTML File](#exporting-results-to-an-html-file) + * [Exporting Results to an JSON File](#exporting-results-to-an-json-file) + * [Command-line Execution of the Log-Parser](#command-line-execution-of-the-log-parser) + * [Memory Guard Rails](#memory-guard-rails) + * [Guard Rail Properties](#guard-rail-properties) + * [File Entry Limitations](#file-entry-limitations) + * [File Size Limitations](#file-size-limitations) + * [Memory Limitations](#memory-limitations) + * [Exporting Anomalies Report](#exporting-anomalies-report) + * [Changelog](#changelog) + * [1.11.3](#1113) + * [1.11.2](#1112) + * [1.11.0](#1110) + * [1.0.10](#1010) + * [1.0.8.2](#1082) + * [1.0.8](#108) + * [1.0.7](#107) + * [1.0.6](#106) + * [1.0.5](#105) + * [1.0.4](#104) + * [1.0.3](#103) + * [1.0.1](#101) ## Installation @@ -84,7 +83,7 @@ The following dependency needs to be added to your pom file: com.adobe.campaign.tests log-parser - 1.11.2 + 1.11.3 ``` @@ -589,7 +588,7 @@ We have the possibility of exporting the anomalies report. This is done by calli ## Changelog -### 1.11.3 (In-Progress) +### 1.11.3 - [#203](https://github.com/adobe/log-parser/issues/203) Have added possibilities, to control, log memory consumption. From 3316aedf089628ecbe7f18158ab8454ee9b0731f Mon Sep 17 00:00:00 2001 From: baubakg Date: Tue, 29 Apr 2025 19:09:24 +0200 Subject: [PATCH 23/25] Updating release notes --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 4238c8a..d9be76c 100644 --- a/README.md +++ b/README.md @@ -591,6 +591,12 @@ We have the possibility of exporting the anomalies report. This is done by calli ### 1.11.3 - [#203](https://github.com/adobe/log-parser/issues/203) Have added possibilities, to control, log memory consumption. +- Updated Dependencies: + - commons-io: 2.19.0 + - commons-csv: 1.14.0 + - testng: 7.11.0 + - jackson-databind: 2.19.0 + - log4j: 2.24.3 ### 1.11.2 From d1751a6c6946f7478afd44e81b7075abe4b17ffe Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 29 Apr 2025 17:29:40 +0000 Subject: [PATCH 24/25] [maven-release-plugin] prepare release log-parser-1.11.3 --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 5bbc857..3503823 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.3-SNAPSHOT + 1.11.3 jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - HEAD + log-parser-1.11.3 From 6efcfcb2cade70287e24bf4add1867dc0f3d21a4 Mon Sep 17 00:00:00 2001 From: adobe-bot Date: Tue, 29 Apr 2025 17:29:41 +0000 Subject: [PATCH 25/25] [maven-release-plugin] prepare for next development iteration --- pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pom.xml b/pom.xml index 3503823..cb06bff 100644 --- a/pom.xml +++ b/pom.xml @@ -14,7 +14,7 @@ 4.0.0 com.adobe.campaign.tests log-parser - 1.11.3 + 1.11.4-SNAPSHOT jar ${project.groupId}:${project.artifactId} A project that allows you to parse logs, and store them in a structured way. @@ -47,7 +47,7 @@ scm:git::https://github.com/adobe/log-parser.git scm:git:https://github.com/adobe/log-parser.git https://github.com/adobe/log-parser/tree/main - log-parser-1.11.3 + HEAD