Application end-to-end response time measurement and decomposition

• US 6,108,700 A
• Filed: 08/01/1997
• Issued: 08/22/2000
• Est. Priority Date: 08/01/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Maccabee, Mark M., Mills, W. Nathaniel III, Turek, John Joseph Edward
• Primary Examiner(s): Dinh, Dung C.
• Application Number:
  US08/904,882
• Time in Patent Office: 1,117 Days
• Field of Search: 709/223, 709/224, 709/101, 709/313, 709/310, 709/318, 709/328, 709/329, 714/38, 714/39, 714/37, 714/47
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5012 determining service availability, e.g. which services are available at a certain point in time
• CPC Class Codes: H04L 41/5032 Generating service level reports

Abstract

A method, computer program product and a program storage device embodying software for measuring of the response time of an application (including distributed applications in a client/server or Internet environment) as perceived by an end-user. One aspect deals with the measurement of components of the response time and relating those components to user response time. In addition, the components of one transaction can be matched (or correlated) to each other even though they are measured on different systems. The generation of events and transactions can be controlled, allowing their creation to occur as close to their point of origin as practical. Both aggregate and detail reporting facilities provide overall performance and availability information as well as exceptions and/or detail transactions including the decomposition of overall availability and performance metrics into smaller measurements representing the contribution made by select transaction components. An interactive reporting facility enables the selection of a level of transaction decomposition desired. This enables the identification of the transaction components that are introducing delays or faults. The system is extensible, enabling the addition of components to the system that extend its measurement and reporting capabilities. In particular, a language has been created to facilitate the definition of the end-to-end business application transactions. Also, select APIs as well as application data structures allow the addition of software and/or hardware modules to extend the system. The system can also adapt to the presence or absence of select streams of events without having to change its mode of operation. Measurement sources that generate events can be dynamically activated and deactivated.

Claims

1. In a system wherein a client requests services involving a multistage computer process, a method for service level management of the process, comprising the steps of:

defining events describing the potential stages of the process;

monitoring and recording events describing the actual stages of the process;

correlating and collating recorded events into one or more transactions describing service level attributes and the actual stages of the process; and

reporting the service level attributes for one or more stages of the process from the one or more transactions.

2. The method of claim 1, wherein said reporting further comprises the step of describing the service level attributes in terms of one of performance, capacity, utilization and availability.

3. The method of claim 1, wherein said correlating and collating further comprises the step of aggregating the recorded events into a subtransaction associated with the process.

4. The method of claim 1, wherein said reporting further comprises the step of aggregating multiple transactions;

and reporting statistics for the multiple transactions.

5. The method of claim 1, further comprising the step of defining a transaction as rules linking events.

6. The method of claim 5, further comprising the steps of:

deriving the rules from an external transaction definition;

generating one or more transactions to be reported on, said transactions based on derived rules,

wherein said monitoring and recording events are limited to events necessary for said reporting.

7. The method of claim 1, further comprising the steps of:

sensors comparing a change in state against rules for generating events; and

generating an event according to the rules, the event describing the change in state, an event identifier, a time stamp, and correlation data.

8. The method of claim 1, wherein the process is a business transaction, further comprising the steps of:

decomposing the business transaction into subtransactions; and

reporting the service level attributes associated with the subtransactions.

9. The method of claim 1, further comprising the steps of:

decomposing the process into one or more levels of subtransactions; and

said reporting includes the step of interactively reporting a requested level of decomposition.

10. The method of claim 1, for extending the measurement or reporting facilities of the system, further comprising the steps of:

providing APIs and application data structures for defining new events;

providing a language for defining new transactions.

11. The method of claim 1, wherein said correlating and collating recorded events into transactions comprises the steps of:

determining if the recorded events starts the transaction and storing the recorded event within the transaction according to predefined transaction generation rules and controls;

linking the recorded event to events stored within the transaction according to predefined transaction generation rules and controls;

determining if the recorded event completes the transaction, linking and storing the recorded event with the transaction; and

storing a completed transaction in response to said determining;

wherein said reporting is in response to said storing.

12. The method of claim 1, further comprising the steps of:

dynamically activating a collection of additional sensor events and deactivating the collection of sensor events;

said sensors generating said additional events; and

said monitoring and recording includes monitoring and recording said additional events, in response to said generating.

13. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for a service level management of client requests for services involving a multistage computer process, said method steps comprising the steps of:

defining events describing the potential stages of the process;

monitoring and recording events describing the actual stages of the process;

correlating and collating recorded events into one or more transactions describing service level attributes and the actual stages of the process; and

reporting the service level attributes for one or more stages of the process from the one or more transactions.

14. The program storage device of claim 13, wherein said reporting further comprises the step of describing the service level attributes in terms of one of performance, capacity, utilization and availability.

15. The program storage device of claim 13, wherein said correlating and collating further comprises the step of aggregating the recorded events into a subtransaction associated with the process.

16. The program storage device of claim 13, wherein said reporting further comprises the step of aggregating multiple transactions;

and reporting statistics for the multiple transactions.

17. The program storage device of claim 13, further comprising the step of defining a transaction as rules linking events.

18. The program storage device of claim 17, further comprising the steps of:

deriving the rules from an external transaction definition;

generating one or more transactions to be reported on, said transactions based on derived rules, wherein said monitoring and recording events are limited to events necessary for said reporting.

19. The program storage device of claim 13, further comprising the steps of:

sensors comparing a change in state against rules for generating events; and

generating an event according to the rules, the event describing the change in state, an event identifier, a time stamp, and correlation data.

20. The program storage device of claim 13, wherein the process is a business transaction, further comprising the steps of:

decomposing the business transaction into subtransactions; and

reporting the service level attributes associated with the subtransactions.

21. The program storage device of claim 13, further comprising the steps of:

decomposing the process into one or more levels of subtransactions; and

said reporting includes the step of interactively reporting a requested level of decomposition.

22. The program storage device of claim 13, for extending the measurement or reporting facilities of the system, further comprising the steps of:

providing APIs and application data structures for defining new events;

providing a language for defining new transactions.

23. The program storage device of claim 13, wherein said correlating and collating recorded events into transactions comprises the steps of:

determining if the recorded events starts the transaction and storing the recorded event within the transaction according to predefined transaction generation rules and controls;

linking the recorded event to events stored within the transaction according to predefined transaction generation rules and controls;

determining if the recorded event completes the transaction, linking and storing the recorded event with the transaction; and

storing a completed transaction in response to said determining;

wherein said reporting is in response to said storing.

24. The program storage device of claim 13, further comprising the steps of:

dynamically activating a collection of additional sensor events and deactivating the collection of sensor events;

said sensors generating said additional events; and

said monitoring and recording includes monitoring and recording said additional events, in response to said generating.

25. A computer program product comprising:

computer usable medium having computer readable program code means embodied therein for a service level management of client requests for services involving a multistage computer process, the computer readable program code means in said computer program product comprising;

computer readable program code means for defining events describing the potential stages of the process;

computer readable program code means for monitoring and recording events describing the actual stages of the process;

computer readable program code means for correlating and collating recorded events into one or more transactions describing service level attributes and the actual stages of the process; and

computer readable program code means for reporting the service level attributes for one or more stages of the process from the one or more transactions.

26. The computer program product of claim 25, wherein said computer readable program code means for reporting further comprises computer readable program code means for describing the service level attributes in terms of one of performance, capacity, utilization and availability.

27. The computer program product of claim 25, wherein said computer readable program code means for correlating and collating further comprises computer readable program code means for aggregating the recorded events into a subtransaction associated with the process.

28. The computer program product of claim 25, wherein said computer readable program code means for reporting further comprises computer readable program code means for aggregating multiple transactions;

and reporting statistics for the multiple transactions.

29. The computer program product of claim 25, further comprising computer readable program code means for defining a transaction as rules linking events.

30. The computer program product of claim 29, further comprising:

computer readable program code means for deriving the rules from an external transaction definition;

computer readable program code means for generating one or more transactions to be reported on, said transactions based on derived rules;

wherein said computer readable program code means for monitoring and recording events are limited to events necessary for said reporting.

31. The computer program product of claim 25, further comprising:

computer readable program code means for comparing a change in state against rules for generating events; and

computer readable program code means for generating an event according to the rules, the event describing the change in state, an event identifier, a time stamp, and correlation data.

32. The computer program product of claim 25, wherein the process is a business transaction, further comprising:

computer readable program code means for decomposing the business transaction into subtransactions; and

computer readable program code means for reporting the service level attributes associated with the subtransactions.

33. The computer program product of claim 25, further comprising:

computer readable program code means for decomposing the process into one or more levels of subtransactions; and

said computer readable program code means for reporting includes computer readable program code means for interactively reporting a requested level of decomposition.

34. The computer program product of claim 25, for extending the measurement or reporting facilities of the system, further comprising:

computer readable program APIs and application data structures for defining new events; and

computer readable program code language means for defining new transactions.

35. The computer program product of claim 25, wherein said computer readable program code means for correlating and collating recorded events into transactions comprises:

computer readable program code means for determining if the recorded events starts the transaction and storing the recorded event within the transaction according to predefined transaction generation rules and controls;

computer readable program code means for linking the recorded event to events stored within the transaction according to predefined transaction generation rules and controls;

computer readable program code means for determining if the recorded event completes the transaction, linking and storing the recorded event with the transaction; and

computer readable program code means for storing a completed transaction in response to said determining;

wherein said reporting is in response to said storing.

36. The computer program product of claim 25, further comprising:

computer readable program code means for dynamically activating a collection of additional sensor events and deactivating the collection of sensor events;

computer readable program code means for generating said additional events; and

said computer readable program code means for monitoring and recording includes computer readable program code means for monitoring and recording said additional events, in response to said computer readable program code means for generating.