Browse Prior Art Database

Method and System for Exploring Log-File Contents as a Filesystem

IP.com Disclosure Number: IPCOM000202398D
Publication Date: 2010-Dec-15
Document File: 3 page(s) / 48K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method and system for exploring log-file contents as a filesystem is disclosed. The method allows a user to browse the log-file using commonly used command-line and shell commands. Additionally, the method allows the user to write shell scripts to perform complex and composite operations using text-processing commands and file I/O commands.

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

Page 01 of 3

Method and System for Exploring Log -File Contents as a Filesystem

Disclosed is a method and system for exploring log-file contents as a filesystem. The method allows a user to browse the log-file using commonly used command-line and shell commands such as, cd, ls, cat, grep, etc. The user may write shell scripts to perform complex and composite operations using text-processing commands and file I/O commands. The user drops log-files or links to the log-file into a designated location.

A FUSE (Filesystem in Userspace) application is provided that parses the log-files and transforms the log-files into a filesystem comprising directories or files. The meta-data elements of a log-file such as, severity, component-id, thread-id, message-id, etc. are mapped to directories and the filtered log-file content into files.

Thereafter, the FUSE application mounts these log-files as a file-system. When the user performs file-system operations or executes commands on these files and directories, the FUSE application transforms the file system operations and commands into corresponding operations in the log-files. Thus, the FUSE application mounts the log-file in the designated directory as a file-system.

In a scenario, consider that "/LogFuseSrc" is the designated directory. The user copies the log-files or links to the log-files into this directory. The log-files in the designated directory may be presented to the user with the following directory structure:

/LogFuse

/LogFuse/Sev/Error

/LogFuse/Sev/Warning

/LogFuse/Sev/Info

In the above directory structure, "Error", "Warning", and "Info" subdirectories are present only when there is a corresponding log message in the log-file.

In the above directory structure, "comp-id1", "comp-id2", and "comp-id3" given below are components present in the log-file.

/LogFuse/Comp/comp-id1

/LogFuse/Comp/comp-id2

/LogFuse/Comp/comp-id3

Further, in the above directory structure, "thrd-id1", "thrd-id2", and "thrd-id3" given below

1


Page 02 of 3

are thread-ids present in the log-file.

/LogFuse/Thread/thrd-id1

/LogFuse/Thread/thrd-id2

The content of the log-file may be filtered and presented in each sub-directory. For example, a file in the '/LogFuse/Sev/Error' may contain log-events that satisfy the query criteria. These log events may be represented by selecting all log-events where sev='error'. In the same manner, a file in the '/LogFuse/Comp/comp-id2' may contain log-events that satisfy the query criteria. The log events in this case, may be represented by selecting all log-events where component='comp-id2'. Further, a file in the '/LogFuse/Thread/thrd-id1' may contain log-events that satisfy the query criteria. These log events may be represented by selecting all log-events where thread-id='thrd-id1'. The files displayed under the Sev/Error directory are not physical files and correspond to results of...