Method for selectively enabling subset of embedded event-making instructions and selecting types and items of event-based data to be collected per enabled instruction
Filing Information
- Patent Number: US5446878
- Application Number: US8326815
- Filing date: 10/20/1994
- Issue date: 08/29/1995
- Predicted expiration date: 02/26/2010
View assignee updates
analyzing 100 million+ documents to uncover your network...- U.S. Classifications: 395/180 · 364/267 ·
- International Classifications: G06F 1130 ·
- International Classifications: 395575;375;600;700 ·
- Related U.S. Application Data:
This is a continuation of application Ser. No. 08/052,227, filed Apr. 22, 1993, now abandoned, which was a continuation of Ser. No. 07/485,372, filed Feb. 26, 1990, now abandoned. - View document at: (opens new window):
USPTO · PAIR · esp@cenet · Patent Family* Related patent documents may or may not exist on these sites
Abstract
An application event collector which is embodied in computer software that collects event-based data. The collector follows a process which includes the steps of: (a) storing definitions of event-marking instructions that have been embedded in the software application, each instruction being capable, when enabled, of collecting event-based data, and the definitions identifying the software application in which the instructions have been embedded and the type of data collected by the instructions; (b) selecting, prior to or during execution of the application, a subset of the event-marking instructions and enabling those instructions; and (c) detecting the enabled event-marking instructions, during execution of the software application, and collecting the data specified by the enabled instructions. The application is divided into layers, each of which may have event-marking instructions embedded in it. These event marking instructions are capable of selectively collecting a some or all of a number of data items and a user can select which of these data items are to be collected. The user can also disable collection of data items.References Cited
U.S. Patent Documents
| Document Number | Assignees | Inventors | Issue/Pub Date |
|---|---|---|---|
| US3906454 | BELL TELEPHONE LABOR INC | Martin | Sep 1975 |
| US4462077 | Bell Telephone Laboratories, Incorporated | York | Jul 1984 |
| US4706080 | Bell Communications Research, Inc. | Sincoskie | Nov 1987 |
| US4802165 | Enteleki, Inc. | Ream | Jan 1989 |
| US4813009 | Tektronix, Inc. | Tallman | Mar 1989 |
| US4845615 | Hewlett-Packard Company | Blasciak | Jul 1989 |
| US4937740 | Cadre Technologies, Inc. | Agarwal et al. | Jun 1990 |
| US5016244 | Honeywell Inc. | Massey, Jr. et al. | May 1991 |
| US5018137 | Digital Equipment Corporation | Backes et al. | May 1991 |
| US5119377 | International Business Machines Corporation | Cobb et al. | Jun 1992 |
Other Publications
| LeBlanc, "Event-Driven Monitoring of Distributed Programs", School of Information and Computer Science, 1985, pp. 515-522. |
| Miller, "A Distributed Programs Monitor for Berkeley Unix", Computer Systems Reserch Group, 1985, pp. 43-54. |
| Cooper, "Pilgrim: A Debugger for Distributed Systems", Cambridge University Computer Laboratory, 1987, pp. 458-465. |
| Miller, "IPS: An Interactive and Automatic Performance Measurement Tool for Parallel and Distributed Programs", University of Wisconsin, 1987, pp. 482-489. |
| Weald, "Data Monitor Facility", Nov., 1987, pp. 1-11. |
| BGS Systems, "Crystal Performance Evaluator for DB2", Crystal Product Family, 1988, pp. 1-2. |
| Monitor, General Information Manual for Monitor for CICS.TM., Landmark Systems Corporation, 1986, pp. 33-38, 49-62, 91-97. |
| Rullo et al., "An Automatic Physical Designer for Network Model Databases", IEEE Transactions on Software Engineering, Sep. 1988, vol. 14, No. 9, New York. |
| Finkelstein et al., "Physical Database Design for Relational Databases", ACM Transactions on Database Systems, vol. 13, No. 1, Mar. 1988, pp. 91-128. |
Referenced By
Patent Family
The current document is not in a family.View Drawings
Independent Claims | See all claims (9)
- 1. A computer implemented process for collecting event-based data for a software application, the process comprising the steps of:prior to execution of the software application:(a) embedding event-marking instructions in the software application, each of said event marking instructions having an enabled state in which event-based data is collected, and a disabled state in which event-based data is not collected; and(b) storing definitions of each of said event-marking instructions that have been embedded in the software application, said definitions identifying the software application in which the corresponding event-marking instructions are embedded, each of said definitions identifying a type superset of possible types of event-based data that may be collected by the corresponding event-marking instructions, each of said types including a corresponding item superset of possible items of event-based data that may be collected for said each type;after embedding of the event-marking instructions in the software application, and prior to or during execution of the software application:(c) selecting a subset of event-marking instructions, said subset including one or more but fewer than all of the event-marking instructions already embedded in the software application;(d) selecting, for each of said selected event-marking instructions in said subset, a type selection of one or more and in some cases fewer than all of said possible types of event-based data to be collected from said type superset in the corresponding definition, and for each of said selected types, an item selection of one or more and in some cases fewer than all of said possible items of event-based data to be collected from said item superset in the corresponding definition;(e) selecting, for each of said selected event-marking instructions in said subset, a time period for collection of said selected items of event-based data; and(f) placing each of said selected event-marking instructions in said subset in said enabled state; andduring execution of the software application:(g) detecting each of said selected event-marking instructions in said enabled subset and collecting each of said selected items of each of said selected types of event-based data specified by said type selection and said item selection, at times falling within said selected time period.
- 2. Computer software for enabling a computer system to carry out a process of collecting event-based data for a software application, the process comprising the steps of:prior to execution of the software application:(a) storing definitions of event-marking instructions that have been embedded in the software application, each of said event-marking instructions having an enabled state in which event-based data is collected, and a disabled state in which event-based data is not collected, said definitions identifying the software application in which the corresponding event-marking instructions are embedded, each of said definitions identifying a type superset of possible types of event-based data that may be collected by the corresponding event-marking instructions, each of said types including a corresponding item superset of possible items of event-based data that may be collected for said each type;after the event-marking instructions have been embedded in the software application, and prior to or during execution of the software application:(b) selecting a subset of event-marking instructions, said subset including one or more but fewer than all of the event-marking instructions already embedded in the software application;(c) selecting, for each of said selected event-marking instructions in said subset, a type selection of one or more and in some cases fewer than all of said possible types of event-based data to be collected from said type superset in the corresponding definition, and for each of said selected types, an item selection of one or more and in some cases fewer than all of said possible items of event-based data to be collected from said item superset in the corresponding definition;(d) selecting, for each of said selected event-marking instructions in said subset, a time period for collection of said selected items of event-based data; and(e) placing each of said selected event-marking instructions in said subset in said enabled state; andduring execution of the software application:(f) detecting each of said selected event-marking instructions in said enabled subset and collecting each of said selected items of each of said selected types of event-based data specified by said type selection and said item selection, at times falling within said selected time period.
