System and method for providing performance statistics for application components

• US 20080168044A1
• Filed: 01/09/2007
• Published: 07/10/2008
• Est. Priority Date: 01/09/2007
• Status: Active Grant

• Current Assignee: Morgan Stanley Services Group Inc. (Morgan Stanley)
• Original Assignee: Morgan Stanley
• Inventors: Brann, John E. T., Barron, Gilbert
• Granted Patent: US 7,685,475 B2
• Time in Patent Office: Days
• US Class Current: 707/4
• 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. An application monitoring method comprising:

capturing raw performance data from one or more components of an 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.

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

3. The method of claim 2, wherein the step of determining a latency average comprises:

determining a small sample size latency average for the one or more components;

determining a medium sample size latency average for the one or more components; and

determining a large sample size latency average for the one or more components.

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

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

6. The method of claim 5, 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.

7. The method of claim 6, further comprising, in response to presenting summary data for a first component to the end user, receiving a request from the end user for summary data for a second component, wherein the first component requires the second component to complete the first component'"'"'s tasks.

8. The method of claim 6, 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.

9. 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.

10. 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.

11. An application monitoring method comprising:

capturing raw performance data from one or more components of an application;

converting the raw performance data of the one or more components to data records having a standard event data format, 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 for the one or more components based on the data records, wherein the summary data comprises a latency average, a load, and a success percentage; and

presenting the summary data to an end user using a web dashboard.

12. 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;

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.

13. The system of claim 12, wherein the one or more event data processors calculate a latency average for the one or more components.

14. The system of claim 13, wherein the one or more event data processors calculate:

a small sample size latency average for the one or more components;

a medium sample size latency average for the one or more components; and

a large sample size latency average for the one or more components.

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

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

17. The system of claim 16, 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.

18. The system of claim 17, 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.

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

20. The system of claim 12, wherein the web dashboard comprises:

a table displaying performance data for a first of the one or more components; and

an optional link, that when activated by the end user, causes the screen to display performance data for a second component, wherein the first component requires the second component to complete the tasks of the first component.

21. The system of claim 12, 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.