System and method for providing performance statistics for application components

• US 7,685,475 B2
• Filed: 01/09/2007
• Issued: 03/23/2010
• Est. Priority Date: 01/09/2007
• Status: Active Grant

• Current Assignee: Morgan Stanley Services Group Inc. (Morgan Stanley)
• Original Assignee: Morgan Stanley Smith Barney LLC (Morgan Stanley)
• Inventors: Brann, John E. T., Barron, Gilbert
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): Mehrmanesh; Elmira
• Application Number:
  US11/651,380
• Publication Number:
  US 20080168044A1
• Time in Patent Office: 1,169 Days
• Field of Search: 714/47, 714/48, 702/186
• US Class Current: 714/47.2
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

An application monitoring method and system. The method may comprise the steps of capturing raw performance data from one or more components of the application, converting the raw performance data of the one or more components to data records having a standard event data format, determining summary data for the one or more components based on the data records, and presenting the summary data to an end user.

Claims

1. A computer-implemented application monitoring method comprising:

capturing raw performance data from one or more components of an application by at least one processor, wherein each of the one or more components of the application performs at least one service required to provide a functionality of the application;

converting the raw performance data of the one or more components to data records having a standard event data format by the at least one processor;

determining summary data for the one or more components by the at least one processor based on the data records, wherein the summary data comprises;

for each of the one or more components, a small sample size latency average, wherein the small sample size latency average is an average latency over a first number of the most recently executed instances of the component;

for each of the one or more components, a medium sample size latency average, wherein the medium sample size latency average is an average latency over a second number of the most recently executed instances of the component, wherein the second number is larger than the first number; and

for each of the one or more components, a large sample size latency average, wherein the large sample size latency average is an average latency over a third number of the most recently executed instances of the component, wherein the third number is larger than the second number; and

presenting to the end user by a server a user interface displaying a first portion of the summary data describing a first component selected from the one or more components and a link that, when activated by the end user causes the user interface to display a second portion of the summary data describing a second component selected from the one or more components, wherein the first component is dependent on the second component such that the first component requires the second component in order for the first component to complete its at least one service.

2. The method of claim 1, wherein the step of determining summary data further comprises determining a load for the one or more components.

3. The method of claim 2, wherein the step of determining summary data further comprises determining a success percentage for the one or more components.

4. The method of claim 3, wherein the step of presenting the summary data to the end user comprises presenting the small sample size latency average, the medium sample size latency average, the large sample size latency average, the load and the success percentage for at least one of the one or more components when requested by the end user.

5. The method of claim 4, wherein the step of determining summary data further comprises determining a service level capacity (SLC) latency percentage for the one or more components, and wherein the step of presenting the summary data further comprises presenting the SLC latency percentage data when requested by the user.

6. The method of claim 1, wherein the step of presenting the summary data comprises presenting the summary data to the end user using a web dashboard.

7. The method of claim 1, wherein the data records having the standard event data format comprise the following data:

a time stamp for a transaction performed by a component;

a component ID;

an indication of whether the transaction was a success; and

a latency value.

8. A computer-implemented application monitoring method comprising:

capturing raw performance data from one or more components of an application by at least one processor, wherein each of the one or more components of the application performs at least one service required to provide a functionality of the application;

converting the raw performance data of the one or more components to data records having a standard event data format by the at least one processor, wherein the data records comprise the following data;

a time stamp for a transaction performed by a component;

a component ID;

an indication of whether the transaction was a success; and

a latency value for the transaction;

determining summary data by the at least one processor for the one or more components based on the data records, wherein the summary data comprises for each of the one or more components a small sample latency average, a medium sample latency average, a large sample latency average, a load, and a success percentage, wherein the small sample size latency average is an average latency over a first number of the most recently executed instances of the component, the medium sample size latency average is an average latency over a second number of the most recently executed instances of the component, and the large sample size latency average is an average latency over a third number of the most recently executed instances of the component, wherein the second number is larger than the first number and the third number is larger than the second number; and

presenting the summary data to an end user as a web dashboard using a server, wherein the web dashboard displays a first portion of summary data describing a first component selected from the one or more components and a link that, when activated by the end user causes the web dashboard to display a second portion of the summary data describing a second component selected from the one or more components, wherein the first component is dependent on the second component such that the first component requires the second component in order for the first component to complete its at least one service.

9. An application monitoring system comprising:

one or more raw data processors that convert raw performance data from one or more components of an application to data records having a standard event data format;

one or more event data processors that calculate summary data for the one or more components based on the data records, wherein the summary data comprises;

for each of the one or more components, a small sample size latency average, wherein the small sample size latency average is an average latency over a first number of the most recently executed instances of the component;

for each of the one or more components, a medium sample size latency average, wherein the medium sample size latency average is an average latency over a second number of the most recently executed instances of the component, wherein the second number is larger than the first number; and

for each of the one or more components, a large sample size latency average, wherein the large sample size latency average is an average latency over a third number of the most recently executed instances of the component, wherein the third number is larger than the second number;

an event summary database that stores the summary data calculated by the event data processors; and

a server that presents the summary data stored in the event summary database to an end user as a user interface, wherein the user interface displays a first portion of the summary data describing a first component selected from the one or more components and a link that, when activated by the end user causes the user interface to display a second portion of the summary data describing a second component selected from the one or more components, wherein the first component is dependent on the second component such that the first component requires the second component in order for the first component to complete its at least one service.

10. The system of claim 9, wherein the one or more event data processors calculate a load for the one or more components.

11. The system of claim 10, wherein the one or more event data processors calculate a success percentage for the one or more components.

12. The system of claim 11, wherein the server is for presenting the small sample size latency average, the medium sample size latency average, the large sample size latency average, the load and the success percentage for at least one of the one or more components when requested by the end user.

13. The system of claim 12, wherein:

the one or more event data processors calculate a service level capacity (SLC) latency percentage for the one or more components; and

the server presents the SLC latency percentage data to the end user.

14. The system of claim 9, wherein the server is a web server that presents the summary data to the end user in a web dashboard.

15. The system of claim 9, wherein the data records having the standard event data format comprise the following data:

a time stamp for a transaction performed by a component;

a component ID;

an indication of whether the transaction was a success; and

a latency value.