Browse Prior Art Database

A Method and System for Identifying Issues with Log Files

IP.com Disclosure Number: IPCOM000237424D
Publication Date: 2014-Jun-18
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Related People

Jon Herron: INVENTOR [+2]

Abstract

A method and system is disclosed for leveraging data within log files and cross referencing it with a source code of an application. The method and system allows developers and other interested parties to quickly identify issues within log files and navigate to the relevant source code of the application. The method and system allows a user to view the log files by reducing noise from the log lines and trends associated with the log lines.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 53% of the total text.

A Method and System for Identifying Issues with Log Files

Abstract

A method and system is disclosed for leveraging data within log files and cross referencing it with a source code of an application.  The method and system allows developers and other interested parties to quickly identify issues within log files and navigate to the relevant source code of the application.  The method and system allows a user to view the log files by reducing noise from the log lines and trends associated with the log lines.

Description

Usually, log files are written to a memory location for debugging and monitoring problems during execution of an application.  These log files are difficult to aggregate, read through and fully comprehend without reference to the source code which generated the log lines.  Moreover, even with the source code, detecting trends across multiple logs files is difficult, not only due to volume but also due to high amount of variable data that each log line contains.

 

Disclosed is a method and system for leveraging data within log files and cross referencing it with a source code of an application.

The method and system disclosed herein takes the log files generated from an application and the source code of that particular application from which the log files have been generated as pre-requisites.  A log parser creates a new “batch ID” which is a unique value allowing data to be associated with a single unique run.  Subsequently, after the batch ID is generated, a source parser begins parsing the source code of the application.  The log parser and the source parser are scheduled to run at designated intervals (e.g. 15 minutes, 1 hour) or they can be run continuously to capture real trends across the log files of the application.

Thereafter, the log parser extracts log statements from the application.  The source parser uses the log statements to dynamically generate a regular expression which is utilized to remove the variable portions from the corresponding log statements.

For example, if the log statement is:

SomeLogger.Debug(“Found %d messages for user %s”, numMessages, userName);

then, the source parser generates a regular expression such as:

s/^(Found )(.*)( messages for user )(.*)$/$1$3/

Subsequently, each log statement is run through the regular expression to compute its SHA-1 hash value.  This hash value is then recorded along with the source location (file and line number(s)) to facilitate cross referencing.

Once the source code of the application is parsed, the log pa...