Monitoring distributed applications

• US 8,230,386 B2
• Filed: 08/23/2007
• Issued: 07/24/2012
• Est. Priority Date: 08/23/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sedukhin, Igor, Chkodrov, Gueorgui Bonov, Kulkarni, Amol Sudhakar, Borsa, Mariusz Gerard, Wu, Haoran Andy, Eshner, Daniel, Zunino, Gilles C. J. A.
• Primary Examiner(s): Wu, Qing
• Application Number:
  US11/844,177
• Publication Number:
  US 20090055838A1
• Time in Patent Office: 1,797 Days
• Field of Search: None
• US Class Current: 717/104
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466

Abstract

The present invention extends to methods, systems, and computer program products for monitoring distributed applications. Declarative application models are used. Operational data for a deployed application can be compared to an application intent expressed in a corresponding declarative application to provide more effective monitoring of application behavior. Application components can subscribe to an event fabric to receive configurations that indicate what events the application is to emit (i.e., publish into the event fabric) for monitoring. Thus, applications essentially subscribe to produce information (as opposed to subscribing to receive information). Monitoring can be dynamically adjusted in response to environment changes.

Claims

1. At a computer system, a method for monitoring a model based distributed application, the method comprising:

an act of accessing a declarative application model describing an application intent, the declarative application model indicating events that are to be emitted from applications deployed in accordance with the application intent;

an act of deploying an application in accordance with the declarative application model;

an act of accessing a declarative observation model, the declarative observation model describing how emitted events, received from an application deployed in accordance with the application intent, are to be aggregated and processed to produce relevant operational data for the application;

an act of compiling the declarative application model and the declarative observation model into an event flow graph for monitoring the behavior of the application, the event flow graph including connected event streams and event operators indicating how to process received events to create operational data for the deployed application;

an act of activating an application event flow based on the event flow graph, the application event flow for receiving and processing emitted events associated with the application to create operational data for the deployed application;

an act of receiving an event associated with the deployed application;

an act of processing the received event in accordance with the activated application event flow to create operational data for the deployed application; and

an act of storing the operational data for use in making subsequent decisions related to the behavior of the deployed application.

2. The method as recited in claim 1, wherein the act activating an application event flow based on the event flow graph comprises activating an application event flow to create operational data indicative of the behavior of the deployed application.

3. The method as recited in claim 1, further comprising prior to activating the application monitoring event flow:

an act of the deployed application subscribing to a monitoring configuration topic within a publish/subscribe event fabric, the monitoring configuration topic corresponding to monitoring configurations that can cause the deployed application to begin emitting events such that the deployed application essentially subscribes to publish information into the publish/subscribe event fabric;

an act of the publish/subscribe event fabric delivering a monitoring configuration to the deployed application based on the deployed application having subscribed to the monitoring configuration topic; and

an act of the deployed application emitting events to the application event topic based on the configuration received on the configuration event topic.

4. The method as recited in claim 1, further comprising:

an act of accessing the stored operational data; and

an act of comparing the operational data to an application intent expressed in the declarative application model to determine if the deployed application is operating as intended.

5. The method as recited in claim 4, further comprising:

an act of determining based on the comparison that the deployed application is not operating in accordance with the application intent; and

an act of modifying the declarative application model to cause any re-deployed application based on the modified declarative application model to more closely approach the application intent.

6. The method as recited in claim 1, wherein the act of compiling the declarative application model and the declarative observation model into an event flow graph comprises compiling the declarative application model and the declarative observation model into an event flow graph that indicates one or more of:

a frequency of executing event operators, where event operators are to be executed, and how many event streams are to be combined to generate operation data for the deployed application.

7. A computer program product for use at a computer system, the computer program product for implementing a method for monitoring a model based distributed application, the computer program product comprising one or more computer readable storage devices having stored thereon computer-executable instructions that, when executed at a processor, cause the computer system to perform the method, including the following:

access a declarative application model describing an application intent, the declarative application model indicating events that are to be emitted from applications deployed in accordance with the application intent;

access a declarative observation model, the declarative observation model describing how emitted events, received from applications deployed in accordance with the application intent, are to be aggregated and processed to produce relevant operational data for applications deployed in accordance with the application intent;

compile the declarative application model and the declarative observation model into an event flow graph for monitoring the behavior of applications deployed in accordance with the application intent, the event flow graph including connected event streams and event operators indicating how to process received events to create the relevant operational data;

activate an application event flow based on the event flow graph, the application event flow for receiving and processing emitted events associated with applications deployed in accordance with the application intent to create the relevant operational data;

receive an event associated with a deployed application, the deployed application having been deployed in accordance with the declarative application model;

process the received event in accordance with the activated application event flow to create operational data for the deployed application; and

store the operational data for use in making subsequent decisions related to the behavior of the deployed application.

8. The computer program product as recited in claim 7, wherein computer-executable instructions that, when executed, cause the computer system to activate an application event flow based on the event flow graph comprise computer-executable instructions that, when executed, cause the computer system to activate an application event flow to create relevant operational data indicative of the behavior of applications deployed in accordance with the application intent.

9. The computer program product as recited in claim 7, further comprising computer-executable instructions that, when executed, cause the computer system to:

subscribe to a monitoring configuration topic within a publish/subscribe event fabric, the monitoring configuration topic corresponding to monitoring configurations that can cause the deployed application to begin emitting events such that the deployed application essentially subscribes to publish information into the publish/subscribe event fabric;

deliver a monitoring configuration to the deployed application based on the deployed application having subscribed to the monitoring configuration topic; and

emit events to the application event topic based on the configuration received on the configuration event topic.

10. The computer program product as recited in claim 7, further comprising computer-executable instructions that, when executed, cause the computer system to:

access the stored operational data; and

compare the operational data to the application intent to determine if the deployed application is operating as intended.

11. The computer program product as recited in claim 10, further comprising computer-executable instructions that, when executed, cause the computer system to:

determine based on the comparison that the deployed application is not operating in accordance with the application intent; and

modify the declarative application model to cause any re-deployed application based on the modified declarative application model to more closely approach the application intent.

12. The computer program product as recited in claim 7, wherein computer-executable instructions that, when executed, cause the computer system to compile the declarative application model and the declarative observation model into an event flow graph comprise computer-executable instructions that, when executed, cause the computer system to compile the declarative application model and the declarative observation model into an event flow graph that indicates one or more of:

a frequency of executing event operators, where event operators are to be executed, and how many event streams are to be combined to generate operation data for the deployed application.

13. A system, the system comprising:

one or more processors;

system memory; and

a monitoring module for monitoring deployed applications, monitoring including;

accessing a declarative application model describing an application intent, the declarative application model indicating events that are to be emitted from applications deployed in accordance with the application intent;

accessing a declarative observation model, the declarative observation model describing how emitted events, received from applications deployed in accordance with the application intent, are to be aggregated and processed to produce relevant operational data for applications deployed in accordance with the application intent;

compiling the declarative application model and the declarative observation model into an event flow graph for monitoring the behavior of applications deployed in accordance with the application intent, the event flow graph including connected event streams and event operators indicating how to process received events to create the relevant operational data;

activating an application event flow based on the event flow graph, the application event flow for receiving and processing emitted events associated with applications deployed in accordance with the application intent to create the relevant operational data;

receiving an event associated with a deployed application, the deployed application having been deployed in accordance with the declarative application model;

processing the received event in accordance with the activated application event flow to create operational data for the deployed application; and

storing the operational data for use in making subsequent decisions related to the behavior of the deployed application.

14. The system as recited in claim 13, wherein activating an application event flow based on the event flow graph comprises activating an application event flow to create relevant operational data indicative of the behavior of applications deployed in accordance with the application intent.

15. The system as recited in claim 13, wherein monitoring further includes:

subscribing to a monitoring configuration topic within a publish/subscribe event fabric, the monitoring configuration topic corresponding to monitoring configurations that can cause the deployed application to begin emitting events such that the deployed application essentially subscribes to publish information into the publish/subscribe event fabric;

delivering a monitoring configuration to the deployed application based on the deployed application having subscribed to the monitoring configuration topic; and

emitting events to the application event topic based on the configuration received on the configuration event topic.

16. The system as recited in claim 13, wherein monitoring further includes:

accessing the stored operational data; and

comparing the operational data to the application intent to determine if the deployed application is operating as intended.

17. The system as recited in claim 16, wherein monitoring further includes:

determining based on the comparison that the deployed application is not operating in accordance with the application intent; and

modifying the declarative application model to cause any re-deployed application based on the modified declarative application model to more closely approach the application intent.

18. The system as recited in claim 13, wherein compiling the declarative application model and the declarative observation model into an event flow graph comprises compiling the declarative application model and the declarative observation model into an event flow graph that indicates one or more of:

a frequency of executing event operators, where event operators are to be executed, and how many event streams are to be combined to generate operation data for the deployed application.