log-parser

This project was created to allow us to parse and analyze log files in order to gather relevant data. It can be used as is or as an SDK. Where you can define your own parsing.

The basic method for using this library is, that you create a definition for your parsing. This definition allows you to parse a set of log files and extract all entries that match this pattern.

Table of contents

• Installation
  • Maven
• Parse Definitions
  • Defining a Parsing
  • Defining an entry
  • How parsing works
  • Code Example
  • Import and Export
• Using the Standard Method
• Using the SDK
• Code Structure
• Searching a organizing log data
  • Search and Filter Mechanisms
  • GroupBy Mechanisms
• Assertions and LogDataAssertions
• 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:

 <dependency>
    <groupId>com.adobe.campaign.tests</groupId>
    <artifactId>log-parser</artifactId>
    <version>1.0.10</version>
</dependency>

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.

Defining a Parsing

Each Parse Definition consists of :

• Title
• A set of entries
• A Padding allowing us to create a legible key
• A key Order which is used for defining the Key

Defining an entry

Each entry for a Parse Definition allows us to define:

• A title for the value which will be found.
• The start pattern of the string that will contain the value (null if in the start of a line)
• The end pattern of the string that will contain the value (null if in the end of a line)
• Case Sensitive search
• Is to be kept. In some cases we just need to find a line with certain particularities, but we don't actually want to store the value.

How parsing works

When you have defined your parsing you use the LogDataFactory by passing it:

1. The log files it should parse
2. The ParseDefinition

By using the StringParseFactory we get a LogData object with allows us to manage the logs data you have found.

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.

@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<ParseDefinitionEntry> definitionList = Arrays.asList(verbDefinition,apiDefinition);

    //Perform Parsing
    Map<String, String> 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.

Using the Standard Method

By default each entry for your lag parsing will be stored as a Generic entry. This means that all values will be stored as Strings. Each entry will have a :

• Key
• A set of values
• The frequence of the key as found in the logs

Using the SDK

Using the log parser as an SDK allow you to define your own transformations and also to override many of the behaviors.

In order to use this feature you need to define a class that extends the class StdLogEntry

Code Structure

Below is a diagram representing the class structure:

Searching and organizing log data

As of versions 1.0.4 & 1.0.5 we have a series of search and organizing the log data.

Search and Filter Mechanisms

We have introduced the filter and search mechanisms. These allow you to search the LogData for values for a given ParseDefinitionEntry. For this we have introduced the following methods:

• isElementPresent
• searchEntries
• filterBy

We currently have the following signatures:

public boolean isEntryPresent(String in_parseDefinitionName, String in_searchValue)
public boolean isEntryPresent(Map<String, Object> in_searchKeyValues)
public LogData<T> searchEntries(String in_parseDefinitionName, String in_searchValue)
public LogData<T> searchEntries(Map<String, Object> in_searchKeyValues)
public LogData<T> filterBy(Map<String, Object> in_filterKeyValues)

In the cases where the method accepts a map we allow the user to search by a series of search terms. Example:

Map<String, Object> l_filterProperties = new HashMap<>();
        l_filterProperties.put("Definition 1", "14");
        l_filterProperties.put("Definition 2", "13");

LogData<GenericEntry> l_foundEntries = l_logData.searchEntries(l_filterProperties)); 

GroupBy Mechanisms

We have introduced the groupBy mechanism. This functionality allows you to organize your results with more detail. Given a log data object, and an array of ParseDefinitionEntry names, we generate a new LogData Object containing groups made by the passed ParseDeinitionEnries and and number of entries for each group.

Let's take the following case:

Definition 1	Definition 2	Definition 3	Definition 4
12	14	13	AA
112	114	113	AAA
120	14	13	AA

If we perform groupBy with the parseDefinition Definition 2, we will be getting a new LogData object with two entries:

Definition 2	Frequence
14	2
114	1

We can also pass a list of group by items, or even perform a chaining of the group by predicates.

Passing a list

We can create a sub group of the LogData by creating group by function:

LogData<GenericEntry> l_myGroupedData = logData.groupBy(Arrays.asList("Definition 1", "Definition 4"));

//or 

LogData<MyImplementationOfStdLogEntry> l_myGroupedData = logData.groupBy(Arrays.asList("Definition 1", "Definition 4"), MyImplementationOfStdLogEntry.class);

In this case we get :

Definition 1	Definition 4	Frequence
12	AA	1
112	AAA	1
120	AA	1

Chaining GroupBy

The GroupBy can also be chained. Example:

LogData<GenericEntry> l_myGroupedData = logData.groupBy(Arrays.asList("Definition 1", "Definition 4")).groupBy("Definition 4");

In this case we get :

Definition 4	Frequence
AA	2
AAA	1

Assertions and LogDataAssertions

As of version 1.0.5 we have introduced the notion of assertions. Assertions can either take a LogData object or a set of files as input.

We currently have the following assertions:

AssertLogData.assertLogContains(LogData<T> in_logData, String in_entryTitle, String in_expectedValue)

AssertLogData.assertLogContains(List<String> in_filePathList, ParseDefinition in_parseDefinition, String in_entryTitle, String in_expectedValue)

AssertLogData.assertLogContains(LogData<T>, String, String ) allows you to perform an assertion on an existing LogData Object.

AssertLogData.assertLogContains(List<String>, ParseDefinition, String, String) allows you to perform an assertion directly on a file.

Exporting Results to a CSV File

We now have the possibility to export the log data results into a CSV file. The file will be a concatenation of the Parse Definition file, suffixed with "-export.csv".

Release Notes

1.0.10

• Moved main code and tests to the package "core"
• #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
• #68 We now present a report of the findings at the end of the analysis.
• #55 We can now export the log parsing results into a CSV file.
• #102 Corrected bug where Log parser could silently stop with no error when confronted with CharSet incompatibilities.

1.0.8.2

• Building with java8.
• Upgraded Jackson XML to remove critical version
• Setting system to work in both java8 and java11. (Java11 used for sonar)

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.