Method and apparatus for tracing troubleshooting events for aiding technical assistance

• US 20040199828A1
• Filed: 04/01/2003
• Published: 10/07/2004
• Est. Priority Date: 04/01/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Moore, Jason Eric, Cabezas, Rafael Graniello, Silvia, Elizabeth, Dang, Anh Tuan
• Application Number:
  US10/405,375
• Publication Number:
  US 20040199828A1
• Time in Patent Office: Days
• US Class Current: 714/39
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/261 by simulating additional hardware, e.g. fault simulation

Abstract

A method and apparatus for tracing troubleshooting events for aiding technical assistance personnel are provided. With the method and apparatus, a user initiates a technical assistance tracing mechanism on his/her client device. The technical assistance tracing mechanism includes event listeners that are registered with the operating system of the client device. These event listeners are notified when, for example, an input device event occurs, when a graphical user interface event occurs, and the like. These events are recorded by the technical assistance tracing mechanism of the present invention as a log of events. This log of events may then be provided to a computing device which is being used by the technical assistance specialist for use in diagnosing and curing the problems encountered by the user. An automated tool may be provided for analyzing the event log and/or emulating an operating system environment so that the event log may be replayed in a graphical manner.

Claims

1. A method of providing event information to a technical assistance specialist, comprising:

recording one or more events that occur in a first computing device associated with a user in an event log;

uploading the event log to a server;

retrieving, by a second computing device associated with the technical assistance specialist, the event log from the server; and

analyzing the event log to determine a probable source of technical difficulty, wherein analyzing the event log includes one or more of;

determining if there are any error events in the event log and identifying a probable source of the error event based on a type of error event present in the event log; and

comparing one or more event patterns to a sequence of one or more events in the event log, determining if an event pattern of the one or more event patterns matches the sequence of one or more events in the event log, and identifying a probable source of technical difficulty based on the event pattern if the event pattern matches the sequence of one or more events in the event log.

2. The method of claim 1, wherein analyzing the event log includes:

emulating an operating environment of the first computing device;

emulating a sequence of one or more events in the event log within the emulated operating environment; and

outputting the emulated operating environment and emulated sequence of events on the second computing device.

3. The method of claim 1, wherein recording one or more events that occur in the first computing device includes:

detecting the occurrence of an event using an event listener in the first computing device; and

generating, by the event listener, an event log entry corresponding to the event, wherein;

the event listener is one of an action listener, a window listener, a mouse listener, a mouse motion listener, a component listener, a focus listener, a list selection listener, and an error event listener, and

the event log entry includes at least one of an event identifier, an identifier of a source of the event, a timestamp, and one or more identifiers of associated operating environment components.

4. The method of claim 1, wherein uploading the event log to a server includes adding a user identifier to the event log prior to uploading, and wherein retrieving the event log from the server includes searching a plurality of event logs stored on the server based on the user identifier.

5. The method of claim 1, wherein identifying a probable source of the error event based on the type of error event includes retrieving an entry in an event database corresponding to the error event, wherein the entry includes information identifying at least one possible source of the error event and at least one suggested solution for the error event.

6. The method of claim 5, wherein the at least one possible source of the error event and at least one suggested solution include a plurality of possible sources of the error event and a plurality of corresponding suggested solutions, and wherein each possible source of the error event includes an associated event pattern that may be matched to an event pattern in the event log to determine which of the plurality of possible sources is the probable source of the error event.

7. The method of claim 1 further comprising:

outputting at least one suggestion for solving the technical difficulty in the first computing device based on the determined probable source of the technical difficulty.

8. A system for providing event information to a technical assistance specialist, comprising:

a client device;

a server coupled to the client device via at least one network; and

a technical assistance specialist computing device coupled to the server via the at least one network, wherein the client device records one or more events that occur in an event log and uploads the event log to the server, and wherein the technical assistance specialist computing device retrieves the event log from the server and analyzes the event log to determine a probable source of technical difficulty in the client device.

9. The system of claim 8, wherein the technical assistance specialist computing device analyzes the event log by determining if there are any error events in the event log and identifying a probable source of the error event based on a type of error event present in the event log.

10. The system of claim 8, wherein the technical assistance specialist computing device analyzes the event log by comparing one or more event patterns to a sequence of one or more events in the event log, determining if an event pattern of the one or more event patterns matches the sequence of one or more events in the event log, and identifying a probable source of technical difficulty based on the event pattern if the event pattern matches the sequence of one or more events in the event log.

11. The system of claim 8, wherein the technical assistance specialist computing device analyzes the event log by emulating an operating environment of the client device, emulating a sequence of one or more events in the event log within the emulated operating environment, and outputting the emulated operating environment and emulated sequence of events on the technical assistance specialist computing device.

12. The system of claim 8, wherein the client device records one or more events that occur in the first computing device by detecting the occurrence of an event using an event listener and generating, by the event listener, an event log entry corresponding to the event.

13. The system of claim 8, wherein the client device adds a user identifier to the event log prior to uploading the event log to the server, and wherein the technical assistance specialist computing device retrieves the event log from the server by sending a request to the server including a user identifier and the server searching a plurality of event logs stored on the server based on the user identifier.

14. The system of claim 9, wherein the technical assistance specialist computing device identifies a probable source of the error event based on the type of error event by retrieving an entry in an event database corresponding to the error event, wherein the entry includes information identifying at least one possible source of the error event and at least one suggested solution for the error event.

15. The system of claim 14, wherein the at least one possible source of the error event and at least one suggested solution include a plurality of possible sources of the error event and a plurality of corresponding suggested solutions, and wherein each possible source of the error event includes an associated event pattern that may be matched to an event pattern in the event log to determine which of the plurality of possible sources is the probable source of the error event.

16. A computer program product in a computer readable medium for providing event information to a technical assistance specialist, comprising:

first instructions for recording one or more events that occur in a first computing device associated with a user in an event log;

second instructions for uploading the event log to a server;

third instructions for retrieving, by a second computing device associated with the technical assistance specialist, the event log from the server; and

fourth instructions for analyzing the event log to determine a probable source of technical difficulty, wherein the fourth instructions for analyzing the event log include one or more of;

instructions for determining if there are any error events in the event log and identifying a probable source of the error event based on a type of error event present in the event log; and

instructions for comparing one or more event patterns to a sequence of one or more events in the event log, determining if an event pattern of the one or more event patterns matches the sequence of one or more events in the event log, and identifying a probable source of technical difficulty based on the event pattern if the event pattern matches the sequence of one or more events in the event log.

17. The computer program product of claim 16, wherein the fourth instructions for analyzing the event log includes:

instructions for emulating an operating environment of the first computing device;

instructions for emulating a sequence of one or more events in the event log within the emulated operating environment; and

instructions for outputting the emulated operating environment and emulated sequence of events on the second computing device.

18. The computer program product of claim 16, wherein the first instructions for recording one or more events that occur in the first computing device include:

instructions for detecting the occurrence of an event using an event listener in the first computing device; and

instructions for generating, by the event listener, an event log entry corresponding to the event, wherein;

the event listener is one of an action listener, a window listener, a mouse listener, a mouse motion listener, a component listener, a focus listener, a list selection listener, and an error event listener, and

the event log entry includes at least one of an event identifier, an identifier of a source of the event, a timestamp, and one or more identifiers of associated operating environment components.

19. The computer program product of claim 16, wherein the instructions for identifying a probable source of the error event based on the type of error event include instructions for retrieving an entry in an event database corresponding to the error event, wherein the entry includes information identifying at least one possible source of the error event and at least one suggested solution for the error event.

20. The computer program product of claim 16, further comprising:

fifth instructions for outputting at least one suggestion for solving the technical difficulty in the first computing device based on the determined probable source of the technical difficulty.