Browse Prior Art Database

Log Analytics and Normalization

IP.com Disclosure Number: IPCOM000248323D
Publication Date: 2016-Nov-15
Document File: 2 page(s) / 20K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for easily parsing a log file and providing relevant information to the user or to a program, which could automate resolutions with the information provided without user interaction.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Log Analytics and Normalization

Retrieving specific information from a log file often requires manual effort (e.g., logging into a machine, finding a log file, reading the log file, etc.). Log information is categorized and easily parsed, but is platform and product independent. Return codes are not consistent from product to product; therefore, determining the cause of errors or other information when installing several products is difficult. In addition, return codes do not provide all of the needed information in text form.

The novel idea is a method for easily parsing a log file and providing relevant information to the user or to a program, which could automate resolutions with the information provided without user interaction.

All errors, warnings, or any type of messages in a log file should have a standard format. For example:

^^^ERROR: some message.^^^, or

^^^WARNING: some warning message.^^^, or ^^^ATTENTION: some message.^^^

The method can provide a standard or a manufacturer can provide an associated specific message format, which the system can easily parse. The system can then display the gathered and information in a dashboard or console.

If a distribution to 100+ machines occurred and many failed, the user can quickly determine the cause via parsing the log in an automated fashion or using an analysis in a tool. The system enables the user to display the results in a console or dashboard without logging into each machine and going through each log file. The information could include important data that could also be tracked or gathered for analytics.

Typical log files work by exiting with a non-zero code and giving a single output message. Most of the time, the information is not enough to resolve the problem without digging deeper into the log file.

In an example use case, the user is preparing to install a product on a large number of machines. The user anticip...