Framework for application monitoring and management

• US 7,640,337 B1
• Filed: 10/28/2004
• Issued: 12/29/2009
• Est. Priority Date: 10/28/2004
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Haverkamp, Laura M., Fultz, David K.
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Fan; Hua
• Application Number:
  US10/975,276
• Time in Patent Office: 1,888 Days
• Field of Search: 709223-225, 709203-207
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466

Abstract

A system is provided for monitoring one or more applications. The system includes a data store to maintain data, such as logs stored in a log file, describing transactions involving at least one of the applications. Some of the data includes context specific information which may be of varying length or content. The system includes agents, adapters, a controller, and a console. The agents communicate the data to the data store according to a configured delivery method. The adapters receive the data from the applications and forward the data to one of the agents. The controller manages the agents and is operable to analyze the data. The console is coupled to the controller to receive command inputs from a user to provide the analysis of the data to the user.

Claims

1. A system for monitoring a plurality of applications, comprising:

a data store configured to maintain data describing transactions involving the plurality of applications, at least some of the data includes context specific information of a length and content that is specific to the processing of the plurality of applications, wherein a first portion of the plurality of applications operate on a first application host, a second portion of the plurality of applications operate on a second application host, a third portion of the plurality of applications operate on a third application host, and a fourth portion of the plurality of applications operate on a fourth application host, wherein the first, second, third, and fourth application hosts are different from each other;

a monitoring host that operates on a host separate from the first, second, third, and fourth application hosts, the monitoring host comprising;

a first data reception mechanism comprising a first message queue manager configured to communicate with both a second message queue manager operating on the first application host and the data store, wherein the second message queue manager comprises a first data delivery mechanism;

a second data reception mechanism comprising a first file loader configured to communicate with both a scheduler operating on the second application host and the data store, wherein the scheduler comprises a second data delivery mechanism;

a third data reception mechanism comprising a first log agent configured to communicate with both a first application monitoring and management log adapter operating on the third application host and the data store, wherein the first application monitoring and management log adapter comprises a third data delivery mechanism;

a fourth data reception mechanism comprising a second log agent configured to communicate with both a second application monitoring and management log adapter operating on the fourth application host and the data store, wherein the second application monitoring and management log adapter comprises a fourth data delivery mechanism; and

a controller that configures at least one of the first, second, third, and fourth data delivery mechanisms based on command inputs, and the controller further configured to analyze the data;

wherein the first data delivery mechanism is configured both to receive data from the first portion of the plurality of applications that are operating on the first application host and to forward the data to the first data reception mechanism, wherein the second data delivery mechanism is configured both to receive data from the second portion of the plurality of applications that are operating on the second application host and to forward the data to the second data reception mechanism, wherein the third data delivery mechanism is configured both to receive data from the third portion of the plurality of applications that are operating on the third application host and to forward the data to the third data reception mechanism, and wherein the fourth data delivery mechanism is configured both to receive data from the fourth portion of the plurality of applications that are operating on the fourth application host and to forward the data to the fourth data reception mechanism; and

a console coupled to the controller and configured to receive the command inputs from a user and to provide the analysis of the data to the user.

2. The system of claim 1, wherein the data is a log.

3. The system of claim 1, wherein at least one of the plurality of applications is a commercial off-the-shelf application.

4. The system of claim 3, wherein the data delivery mechanism on at least one of the first, second, third, and fourth application hosts includes one of the first and second application monitoring and management commercial off-the-shelf log adapters configured to receive the data from the commercial off-the-shelf application according to an interface determined by the commercial off-the-shelf application.

5. The system of claim 1, wherein one of the first, second, third, and fourth data delivery mechanisms on at least one of the first, second, third, and fourth application hosts includes the second message queue manager coupled to communicate with one of the plurality of applications to receive the data from the one of the plurality of applications, the second message queue manager configured to arrange the data as a message;

wherein the monitoring host includes a message agent that receives the message, extracts the data from the message, and sends the data to the data store, the controller configured to manage the message agent, and

the first, second, third, and fourth data reception mechanisms further include the first message queue manager configured to communicate the message between the second message queue manager and the message agent.

6. The system of claim 5, wherein the first message queue manager and the second queue message manager are MQ Series message queue managers.

7. The system of claim 5, wherein the first message queue manager and the second message queue manager are Java Message Service message queue managers.

8. The system of claim 1, wherein one of the first, second, third, and fourth data delivery mechanisms on at least one of the first, second, third, and fourth application hosts includes a plurality of files associated with one of the plurality of applications, the files containing the data describing the processing of the one of the plurality of applications,

wherein the second data reception mechanism includes the file loader component configurable via the controller, the file loader component configured to extract the data from the plurality of files and to send the data to the data store, the file loader component configured on the monitoring host, and

the second data delivery mechanism further includes the scheduler component associated with the one of the plurality of applications and the scheduler component configured to periodically copy the files to the file loader component.

9. The system of claim 1, wherein context specific information includes information related to debugging the at least one of the plurality of applications, the first, second, third, and fourth data delivery mechanisms configured to receive the context specific information.

10. The system of claim 1, wherein the data describes a sequence of processing of one of the transactions.

11. The system of claim 1, wherein the command inputs to the console include selection of a level of detail of the data describing the transactions and wherein the reports based on the data contain the level of detail selected in the command input.

12. The system of claim 1, further comprising:

a rules data store containing a plurality of analysis rules for evaluating the data describing the transactions; and

an alarmer configured to use the analysis rules to evaluate the data of the transactions and to provide a notice for delayed and failed transactions.

13. A computer implemented method for monitoring and managing a plurality of applications, comprising:

maintaining, on a data store, data describing transactions involving the plurality of applications, at least some of the data includes context specific information of a length and content that is specific to the processing of the plurality of applications;

operating a first portion of the plurality of applications on a first application host;

operating a second portion of the plurality of applications on a second application host;

operating a third portion of the plurality of applications on a third application host;

operating a fourth portion of the plurality of applications on a fourth application host, wherein the first, second, third, and fourth application hosts are different from each other;

operating a monitoring host on a host separate from the first, second, third, and fourth application hosts, the monitoring host comprising;

a first data reception mechanism comprising a first message queue manager communicating with both a second message queue manager operating on the first application host and the data store, wherein the second message queue manager comprises a first data delivery mechanism;

a second data reception mechanism comprising a first file loader communicating with both a scheduler operating on the second application host and the data store, wherein the scheduler comprises a second data delivery mechanism;

a third data reception mechanism comprising a first log agent communicating with both a first application monitoring and management log adapter operating on the third application host and the data store, wherein the first application monitoring and management log adapter comprises a third data delivery mechanism;

a fourth data reception mechanism comprising a second log agent communicating with both a second application monitoring and management log adapter operating on the fourth application host and the data store, wherein the second application monitoring and management log adapter comprises a fourth data delivery mechanism; and

a controller configuring at least one of the first, second, third, and fourth data delivery mechanisms based on command inputs, and the controller further analyzing the data;

wherein the first data delivery mechanism both receives data from the first portion of the plurality of applications that are operating on the first application host and forwards the data to the first data reception mechanism, wherein the second data delivery mechanism both receives data from the second portion of the plurality of applications that are operating on the second application host and forwards the data to the second data reception mechanism, wherein the third data delivery mechanism both receives data from the third portion of the plurality of applications that are operating on the third application host and forwards the data to the third data reception mechanism, and wherein the fourth data delivery mechanism both receives data from the fourth portion of the plurality of applications that are operating on the fourth application host and forwards the data to the fourth data reception mechanism;

receiving, at a console coupled to the controller, the command inputs from a user; and

providing the analysis of the data to the user.

14. The method of claim 13, wherein the context specific information is further defined as a first context specific information based on the first application and a second context specific information based on the second application, the first and second context specific information having different lengths and content.

15. The method of claim 13, wherein at least one of the plurality of applications employs the configured configurable communication mechanism.

16. The method of claim 15, further including:

invoking by at least one of plurality of applications a first method to initialize the collection of the data;

invoking by at least one of the plurality of applications a second method to record the beginning of a transaction;

invoking by at least one of the plurality of applications a third method to record the end of the transaction; and

invoking by at least one of the plurality of applications a fourth method to terminate the collection of the data.

17. The method of claim 13, wherein at least one of plurality of applications executes on a first system, the data store is external to the first system, and the analyzing the data occurs on a second system.

18. The method of claim 13, wherein at least one of the plurality of applications is a commercial off-the-shelf application.

19. The method of claim 13, further including:

identifying at least one of the data that indicate at least one of the plurality of applications has failed to meet a service level agreement.

20. The method of claim 19, further including:

displaying a message on a user interface identifying the transaction of at least one of the plurality of applications that has failed to meet the service level agreement, the message displayed in a color coded to the severity of the failure to meet the service level agreement.

21. The method of claim 13, further comprising:

using the data in the data store according to the user defined level of detail to generate a report on at least one of the plurality of applications; and

changing the configuration of the environment of at least one of the plurality of applications based on the report.