Browse Prior Art Database

A method of recording GUI screenshot and browse log with the server log together

IP.com Disclosure Number: IPCOM000227413D
Publication Date: 2013-May-07
Document File: 2 page(s) / 71K

Publishing Venue

The IP.com Prior Art Database

Abstract

For web client/server application developer, they always need to do the development and issue investigation on both client and server. And the log information is in text. There is no graphical and visual way to analyse the log file. developers need separate steps and GUI screenshot to investigate the problem. This invention is about recording web client GUI action, screenshot and browser log and server logs in a unified mode. Then if needed, people can read and search the logs from one place on server with sequential client request/response thread and screenshot.

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

Page 01 of 2

A method of recording GUI screenshot and browse log with the server log together

Field of this invention

This invention is about recording web client GUI screenshot and browse log and server logs in a unified mode. Then if needed, people can read and search the logs from one place on server with sequential client request/response thread and screenshot.

Overview of the method of recording unified log

For web client/server application developer, they always need to do the development and issue investigation on both client and server. And the log information is in text. developers need separate steps and GUI screenshot to investigate the problem. Unfortunately, they usually need to check all the information individually. The unified log is a mechanism to record and review client and server log files, client actions, client screenshot and browser log together. Also the logs can show the Client GUI action, request/response and screenshot thread by each client or session.

The problem of solved by the invention

The problem of web client/server application log files is that the files are record individually. All the logs are in text. There is no graphical and visual way to analyse the log file. It is NOT easy to identify the GUI steps that cause the issue from the log files. And it's hard to classify which server logs are generated by the same client. It's hard to classify the whole request/response thread

There have been some methods proposed to address this problem. In this invention, a new method is provided to address the same problem, to record the unified log files. Firstly, the browser plugin will get the browse logs, screenshots, GUI actions(such as click a button) and generate a client ID at the same time. Then the logs, actions and screenshots of client side will be sent to server side together with the client ID. The server side will record all this information with server logs together. Then when people want to review the logs, the client and server side logs c...