Monitoring and automatically managing applications

• US 9,176,759 B1
• Filed: 03/16/2012
• Issued: 11/03/2015
• Est. Priority Date: 03/16/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Sahasranaman, Vivek, Risbood, Pankaj, Sarda, Parag Kacharulal, Shenoy, Vittaldas Sachin, Jain, Rohit
• Primary Examiner(s): Lee, Adam
• Application Number:
  US13/422,575
• Time in Patent Office: 1,327 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

This document generally describes techniques, methods, systems, and computer program products for monitoring and managing applications running on virtual machines (VMs).

Claims

1. A computer-implemented method comprising:

receiving, by one or more computing devices and from an agent running on a virtual machine according to a configuration to run an application, application-level performance statistics of the application running on the virtual machine, wherein the application-level performance statistics measure the performance of the application, including a current level of efficiency with which the application is processing requests, the application-level performance statistics being independent of host-level performance statistics that are indicative of the host status of the virtual machine on which the application is running;

determining, using one or more computing devices, whether the application-level performance statistics satisfy one or more triggers of the application, wherein each of the triggers results in one or more actions that are applied to the application, and wherein at least a first trigger is satisfied when the application-level performance statistics are determinative of the application having experienced a performance degradation;

causing at least one of the actions to be performed responsive to the determination of whether the application-level performance statistics satisfy one or more of the triggers, wherein the at least one of the actions performed in response to the first trigger being satisfied comprises causing an additional virtual machine to be instantiated according to the configuration with an instance of the application; and

determining whether the application has experienced an anomalous event responsive to a comparison of the application-level performance statistics of the application to application-level performance statistics of other instances of the application that are running on other virtual machines.

2. The method of claim 1, wherein the at least one of the actions performed comprises causing the virtual machine to be shutdown.

3. The method of claim 1, further comprising aggregating the application-level performance statistics for the application and the virtual machine with application-level performance statistics received for other instances of the application that are running on other virtual machines;

wherein the one or more triggers are evaluated and the one or more actions are caused to be performed based on the aggregated application-level performance statistics.

4. The method of claim 1, wherein the application-level performance statistics are repeatedly received by the one or more computing devices and time coded upon receipt;

and wherein determining whether the application-level performance statistics satisfy the one or more triggers comprises determining whether application-level performance statistics for the application received over a time period satisfy the one or more triggers.

5. The method of claim 1, wherein the application-level performance statistics include information determining a number of requests received by the application over a period of time.

6. The method of claim 1, wherein the application-level performance statistics include information determining an average latency for the application to process received requests over a period of time.

7. The method of claim 1, wherein the application-level performance statistics include information determining an average amount of data transferred by the application per received request over a period of time.

8. The method of claim 1, wherein the application-level performance statistics include information determining a number of errors encountered by the application over a period of time.

9. The method of claim 1, wherein the application-level performance statistics include information determining a number of items that are currently pending in a task queue for the application.

10. The method of claim 9, wherein the application-level performance statistics include information indicating determining a number of tasks from the task queue that were performed by the application over a period of time.

11. The method of claim 1, wherein the application-level performance statistics include information indicating determining a number of operations taking more than a threshold amount of time to process that are performed by the application over a period of time.

12. The method of claim 11, wherein the operations include database queries.

13. The method of claim 1, further comprising causing the application, the virtual machine, or a host computing device that is running the virtual machine to restart or reboot in response to determining that the anomalous event has occurred.

14. The method of claim 1, wherein the application-level performance statistics are received from the agent running on the virtual machine, the agent obtaining the application-level performance statistics from one or more plugins specific to the application and running on the virtual machine;

and wherein the plugins communicate with the application through one or more application programming interfaces used by the application.

15. A computer program product including instructions stored on a non-transitory computer-readable medium that, when executed, cause a processor to perform operations comprising:

receiving from an agent running on a virtual machine according to a configuration to run an application, application-level performance statistics of the application running on the virtual machine, wherein the application-level performance statistics measure the performance of the application, including a current level of efficiency with which the application is processing requests, the application-level performance statistics being independent of host-level performance statistics that are indicative of the host status of the virtual machine on which the application is running;

determining, using one or more computing devices, whether the application-level performance statistics satisfy one or more triggers of the application, wherein each of the triggers results in one or more actions that are applied to the application, and wherein at least a first trigger is satisfied when the application-level performance statistics are determinative of the application having experienced a performance degradation;

causing at least one of the actions to be performed responsive to the determination of whether the application-level performance statistics satisfy one or more of the triggers, wherein the at least one of the actions performed in response to the first trigger being satisfied comprises causing an additional virtual machine to be instantiated according to the configuration with an instance of the application; and

determining whether the application has experienced an anomalous event responsive to a comparison of the application-level performance statistics of the application to application-level performance statistics of other instances of the application that are running on other virtual machines.

16. The computer program product of claim 15, wherein the application-level performance statistics are repeatedly received and time coded upon receipt;

and wherein determining whether the application-level performance statistics satisfy the one or more triggers comprises determining whether application-level performance statistics for the application received over a time period satisfy the one or more triggers.

17. The computer program product of claim 15, wherein the operations further comprise aggregating the application-level performance statistics for the application and the virtual machine with application-level performance statistics received for other instances of the application that are running on other virtual machines;

wherein the one or more triggers are evaluated and the one or more actions are caused to be performed based on the aggregated application-level performance statistics.

18. A system comprising:

one or more computer processors; and

instructions that, when executed, cause the one or more computing devices to perform operations comprising;

receiving from an agent running on a virtual machine according to a configuration to run an application, application-level performance statistics of the application running on the virtual machine, wherein the application-level performance statistics measure the performance of the application, including a current level of efficiency with which the application is processing requests, the application-level performance statistics being independent of host-level performance statistics that are indicative of the host status of the virtual machine on which the application is running;

determining, using one or more computing devices, whether the application-level performance statistics satisfy one or more triggers of the application, wherein each of the triggers results in one or more actions that are applied to the application, and wherein at least a first trigger is satisfied when the application-level performance statistics are determinative of the application having experienced a performance degradation;

causing at least one of the actions to be performed responsive to the determination of whether the application-level performance statistics satisfy one or more of the triggers, wherein the at least one of the actions performed in response to the first trigger being satisfied comprises causing an additional virtual machine to be instantiated according to the configuration with an instance of the application; and

determining whether the application has experienced an anomalous event responsive to a comparison of the application-level performance statistics of the application to application-level performance statistics of other instances of the application that are running on other virtual machines.

19. The system of claim 18, wherein the at least one of the actions performed comprises causing the virtual machine to be shutdown.

20. The system of claim 18, wherein the operations further comprise aggregating the application-level performance statistics for the application and the virtual machine with application-level performance statistics received for other instances of the application that are running on other virtual machines;

wherein the one or more triggers are evaluated and the one or more actions are caused to be performed based on the aggregated application-level performance statistics.