Event log management system

• US 20070260932A1
• Filed: 04/11/2006
• Published: 11/08/2007
• Est. Priority Date: 04/11/2006
• Status: Abandoned Application

• Current Assignee: Verigy Limited (Advantest Corporation)
• Original Assignee: Verigy Limited (Advantest Corporation)
• Inventors: Rogel-Favila, Ben, Prichard, Ryan
• Application Number:
  US11/402,113
• Publication Number:
  US 20070260932A1
• Time in Patent Office: Days
• US Class Current: 714/39
• CPC Class Codes: G06F 11/2215 to test error correction or detection circuits
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

The present invention is an event log management system and method for monitoring the reliability of test systems. An event log management system includes a data store which stores at least one tester configuration file, a hardware independent event capture function which captures events from at least one monitored tester associated with one of the at least one test configuration files, a graphical user interface which receives issue information from a user, and a server which manages storage and tracking of the captured events.

Claims

1. An Event Log Management System, comprising:

a data store which stores at least one tester configuration file;

a hardware independent event capture function which captures events from at least one monitored tester associated with one of the at least one test configuration files;

a graphical user interface which receives issue information from a user; and

a server which receives the issue information from the graphical user interface and creates an issue data element corresponding to the issue information, and which receives the captured events from the event capture function and stores the captured events in an event store, associating respective captured events with corresponding respective issues.

2. The system of claim 1, wherein the graphical user interface is web enabled.

3. The system of claim 1, wherein the hardware independent event capture function comprises a Web Services application program interface (API).

4. The system of claim 1, wherein the at least one tester configuration file is implemented in XML.

5. The system of claim 1, further comprising a reporting function which reports events associated with a particular one of the at least one testers.

6. The system of claim 1, further comprising a reporting function which reports events associated with a particular issue.

7. The system of claim 1, wherein the issue data element created by the server is implemented as an XML file.

8. The system of claim 7, wherein when the server receives a particular captured event from the event capture function, the server determines which particular issue, if any, of the issues the particular captured event is associated with, and stores the particular captured event in the XML file comprising the issue data element associated with the particular issue, and if the particular capture event is not associated with any issue, stores the particular captured event in an XML file comprising a default issue data element that is associated with a default issue.

9. A method for managing events of at least one tester, comprising:

obtaining at least one tester configuration file;

automatically capturing events from at least one monitored tester associated with one of the at least one test configuration files using a hardware independent interface;

receiving issue information; and

providing a server which creates an issue data element corresponding to the issue information, and which stores the captured events in an event store, and associates respective captured events with corresponding respective issues.

10. The method of claim 9, wherein the step of receiving issue information is performed through a web enabled graphical user interface.

11. The method of claim 9, wherein the step of automatically capturing events from at least one monitored tester comprises receiving events from the at least one monitored tester using a hardware independent event Web Services application program interface (API).

12. The method of claim 9, further comprising:

reporting events associated with a particular one of the at least one testers into a report, formatting the events in the report according to event attributes as defined in the tester configuration file associated with the particular one of the at least one testers.

13. The method of claim 9, further comprising a reporting function which reports events associated with a particular issue into a report, formatting the events in the report according to event attributes as defined in the tester configuration file associated with the particular one of the at least one testers.

14. The method of claim 13, wherein when the server receives a particular captured event from the event capture function, determines which particular issue, if any, of the issues the particular captured event is associated with, and stores the particular captured event in an XML issue file associated with the particular issue, and if the particular capture event is not associated with any issue, stores the particular captured event in an XML default issue file associated with a default issue.

15. An Event Log Management System, comprising:

a data store which stores at least one tester configuration file, each tester configuration file implemented in XML and comprising one or more event type definitions and corresponding attribute definitions;

a hardware independent event capture function which captures events from at least one monitored tester associated with one of the at least one test configuration files;

a Web enabled graphical user interface which receives issue information associated with a user perceived condition from a user; and

a server which creates an issue file implemented in XML corresponding to and encapsulating the issue information, and which encapsulates captured events captured by the hardware independent event capture function in respective issue files corresponding to respective issues to which the respective captured events are associated.

16. The system of claim 15, wherein the hardware independent event capture function comprises a Web Services application program interface (API).

17. The system of claim 15, further comprising a reporting function which reports events associated with a particular one of the at least one testers in an XML report file.

18. The system of claim 15, further comprising a reporting function which reports events associated with a particular issue in an XML report file.