Centralized monitoring and early warning operations console

• US 7,069,184 B1
• Filed: 10/09/2003
• Issued: 06/27/2006
• Est. Priority Date: 10/09/2003
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Weaver, Chris R., Laura, Joseph G., Brennan, Gerald Michael, Durden, Kenneth Dale, Barger, Karl W.
• Primary Examiner(s): Barlow, John
• Assistant Examiner(s): VO, HIEN XUAN
• Application Number:
  US10/681,930
• Time in Patent Office: 992 Days
• Field of Search: 702/186, 702/182, 702/183, 709/224, 709/228, 709/200, 709/223, 709/217, 709/220, 709/227, 717/108, 717/116, 717/120, 704/270.1
• US Class Current: 702/186
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 2201/81 Threshold

Abstract

An application monitoring system is provided. The application monitoring system includes a monitor component to monitor statistics related to an application in operation. A reporting component is in communication with the monitor component and is operable to capture the statistics of the application in operation monitored by the monitor component. A trigger component analyzes the statistics of the application monitored by the monitor component and compares the statistics of the application with a threshold and generates a trigger signal based on the relationship of the statistics of the threshold. A dashboard component is operable to identify the application to monitor and provide an application threshold. A method of monitoring an application using an application monitoring system is also provided.

Claims

1. An application monitoring system, comprising:

a monitor component to monitor statistics related to an application in operation;

a reporting component in communication with the monitor component and operable to report the statistics of the application in operation monitored by the monitor component;

a trigger component to analyze the statistics of the application monitored by the monitor component and compare the statistics of the application with a threshold and generate a trigger signal based on the relationship of the statistics to the threshold; and

a dashboard component operable to identify the monitored application and provide the threshold related to the monitored application;

wherein the monitor component is operable to monitor statistics of a plurality of applications in operation.

2. The application monitoring system of claim 1, wherein the dashboard component includes a user interface.

3. The application monitoring system of claim 2, wherein the dashboard component is coupled to the trigger component and operable to display a message on the user interface of the dashboard component in response to the trigger signal.

4. The application monitoring system of claim 2, wherein the user interface of the dashboard component is further defined as web enabled.

5. The application monitoring system of claim 1, further comprising a repository operable to maintain an error report associated with errors of the application.

6. The application monitoring system of claim 1, further comprising a recovery component operable to initiate a recovery of the application.

7. The application monitoring system of claim 6, wherein the recovery is further defined as restarting the application.

8. The application monitoring system of claim 6, wherein the recovery component is coupled to receive a recovery signal from the trigger component based on the threshold.

9. The application monitoring system of claim 1, wherein the threshold is further defined as a business rule.

10. The application monitoring system of claim 1, wherein the threshold is further defined as a predefined threshold.

11. The application monitoring system of claim 1, wherein the statistics of the application monitored by the monitor component are further defined as an output of the application.

12. The application monitoring system of claim 1, wherein the statistics of the application monitored by the monitor component are further defined as a cycle of the application.

13. The application monitoring system of claim 1, wherein the monitor component monitors a first application on a first system and a second application on a second system.

14. The application monitoring system of claim 13, wherein the first system is a mainframe computer system and wherein the second application is a non-mainframe computer system.

15. An application monitoring system, comprising:

a monitor component to monitor an application in operation;

a trigger component to analyze the statistics of the application monitored by the monitor component and compare the statistics of the application with a threshold and generate a trigger signal based on the relationship of the statistics to the threshold;

a dashboard component operable to identify the application to monitor and provide the threshold related to the application to monitor; and

a requestor component coupled to promote communication between the dashboard component and the monitor component, wherein the monitor component is further defined as an information service layer.

16. The application monitoring system of claim 15, wherein the information service layer includes:

a control system having a registry and operable to communicate with the requestor having a request for data, the request for data including a source identifier and a data identifier;

a client service operable to register with the control system and receive the request for data, the client service further operable to communicate a requested data related to the data identifier to the requestor; and

a retrieval service operable to use at least a portion of the source identifier to retrieve the requested data related to the data identifier and communicate the requested data to the client service.

17. The application monitoring system of claim 16, wherein the request for data from the requestor is further defined as an extensible mark-up language tag.

18. The application monitoring system of claim 15, wherein the data identifier is further defined as an extensible mark-up language string having a plurality of tags identifying the a desired data.

19. The application monitoring system of claim 15, wherein the application being monitored is defined as a mainframe process.

20. The application monitoring system of claim 15, wherein the application being monitored is defined as output from a computer program.

21. The application monitoring system of claim 15, wherein the application being monitored is defined as a telephony process.

22. The application monitoring system of claim 15, wherein the application being monitored is defined as a billing cycle process.

23. A method of monitoring an application, comprising:

selecting an application having data related to metrics of the application to be monitored;

providing a service layer for retrieving data, the service layer including;

a control system having a registry and operable to receive a request for data, the request including a source identifier and a data identifier,

a client service operable to register with the control system and receive the request for data, the client service further operable to communicate a requested data related to the data identifier, and

a retrieval service operable to utilize at least a portion of the source identifier to retrieve the requested data related to the data identifier and communicate the requested data to the client service;

requesting the data from the service layer, the data related to metrics of the application;

receiving the data via the information service layer;

establishing a threshold for the data;

monitoring the data related to metrics of the application;

analyzing the data based on the threshold established for the data; and

signaling when the data exceeds the threshold.

24. The method of claim 23, wherein the request for data from the service layer is further defined as an extensible mark-up language tag.

25. The method of claim 23, wherein the service layer is further defined as a mainframe service layer and wherein the application is a mainframe application.

26. The method of claim 23, wherein the service layer is further defined as a mainframe service layer and wherein the application is a non-mainframe application.

27. The application monitoring system of claim 23, wherein the application being monitored is defined as a telephony process.

28. The application monitoring system of claim 23, wherein the application being monitored is defined as a billing cycle process.