Server performance correction using remote server actions

Patent metadata

Field	Value
Publication number	US-9658917-B2
Application number	US-201414175945-A
Country	US
Kind code	B2
Filing date	Feb 7, 2014
Priority date	Feb 7, 2014
Publication date	May 23, 2017
Grant date	May 23, 2017

Abstract

Business transactions and the nodes processing the transactions may be monitored. Actions may be applied to one or more nodes when a performance issue is detected. A performance issue may relate to a metric associated with a transaction or node that processes the transaction. If a performance metric does not satisfy a health rule, the policy determines which action should be performed to correct the performance of the node. The corrective action may be applied to a node other than the node at which the performance metric is associated with. For example, if a performance metric for a first node does not satisfy a threshold, the corrective action may be applied to a second node. When a solution applied to a second node is found to correct the problem in first node, the solution may be applied to the other nodes experiencing the same problem.

First claim

What is claimed is:

1. A method for monitoring a distributed business transaction over a distributed system of nodes, the method comprising:
receiving, by a controller on a server, performance data associated with the nodes that process a distributed business transaction, the performance data received from the agents installed at the nodes;
detecting, by the controller, a performance issue with one of the nodes based on the received performance data;
selecting one or more of the nodes other than the node associated with the detected performance issue, the one or more of the other nodes associated with a cause of the detected performance issue and the selecting being based on a parameter associated with the node associated with the detected performance issue; and
applying a corrective action to the selected one or more of the nodes other than the node associated with the detected performance issue to address the cause of the detected performance issue; and
monitoring the node associated with the detected performance issue to determine whether subsequent performance data received for the node associated with the detected performance issue improve after the corrective action is applied to the selected one or more of the nodes other than the node associated with the detected performance issue.

2. The method of claim 1 , wherein detecting the performance issue includes comparing the received performance data against one or more health rules.

3. The method of claim 2 , including determining the corrective action to apply based on a violation of the one or more of the health rules.

4. The method of claim 1 , wherein the corrective action is applied to the one or more of the nodes other than the node associated with the detected performance issue to address a performance issue associated with a request initiated by the node associated with the detected performance issue, wherein the performance issue associated with the request is caused by a lack of resources at the one or more of the nodes other than the node associated with the detected performance issue.

5. The method of claim 1 , including:
determining a metric for the node associated with the detected performance issue.

6. The method of claim 1 , including instructing the agent or agents installed on the selected one or more nodes other than the node associated with the detected performance issue to apply the corrective action.

7. The method of claim 1 , wherein the corrective action includes creating additional instances of virtual machines, restarting a machine, executing a string of commands via script code, configuring a new or restarted virtual machine, installing an agent in a virtual machine, applying a configuration to a virtual machine or application, or restarting an application.

8. The method of claim 1 , including:
determining based on the monitoring that the corrective action applied to the selected one or more of the nodes other than the node associated with the detected performance issue does not result in the detected performance issue being corrected; and
applying another corrective action to the selected one or more of the nodes other than the node associated with the detected performance issue.

9. The method of claim 1 , including:
selecting the corrective action from a list of available action sorted based on a probability of addressing the detected performance issue.

10. The method of claim 1 , wherein each node includes one or more application servers.

11. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform operations for monitoring a distributed business transaction, the operations including:
receiving, by a controller on a server, performance data associated with the nodes that process a distributed business transaction, the performance data received from the agents installed at the nodes;
detecting, by the controller, a performance issue with one of the nodes based on the received performance data;
selecting one or more of the nodes other than the node associated with the detected performance issue, the one or more of the other nodes associated with a cause of the detected performance issue and the selecting being based on a parameter associated with the node associated with the detected performance issue; and
applying a corrective action to the selected one or more of the nodes other than the node associated with the detected performance issue to address the cause of the detected performance issue; and
monitoring the node associated with the detected performance issue to determine whether subsequent performance data received for the node associated with the detected performance issue improve after the corrective action is applied to the selected one or more of the nodes other than the node associated with the detected performance issue.

12. The non-transitory computer readable storage medium of claim 11 , wherein detecting the performance issue includes comparing the received performance data against one or more health rules.

13. The non-transitory computer readable storage medium of claim 12 , the operations including determining the corrective action to apply based on a violation of the one or more of the health rules.

14. The non-transitory computer readable storage medium of claim 11 , wherein the corrective action is applied to the one or more of the nodes other than the node associated with the detected performance issue to address a performance issue associated with a request initiated by the node associated with the detected performance issue, wherein the performance issue associated with the request is caused by a lack of resources at the one or more of the nodes other than the node associated with the detected performance issue.

15. The non-transitory computer readable storage medium of claim 11 , the operations including:
determining a metric for the node associated with the detected performance issue.

16. The non-transitory computer readable storage medium of claim 11 , the operations including instructing the agent or agents installed on the selected one or more nodes other than the node associated with the detected performance issue to apply the corrective action.

17. The non-transitory computer readable storage medium of claim 11 , wherein the corrective action includes creating additional instances of virtual machines, restarting a machine, executing a string of commands via script code, configuring a new or restarted virtual machine, installing an agent in a virtual machine, applying a configuration to a virtual machine or application, or restarting an application.

18. The non-transitory computer readable storage medium of claim 11 , the operations including:
determining based on the monitoring that the corrective action applied to the selected one or more of the nodes other than the node associated with the detected performance issue does not result in the detected performance issue being corrected; and
applying another corrective action to the selected one or more of the nodes other than the node associated with the detected performance issue.

19. The non-transitory computer readable storage medium of claim 11 , the operations including:
selecting the corrective action from a list of available action sorted based on a probability of addressing the detected performance issue.

20. The non-transitory computer readable storage medium of claim 11 , wherein each node includes one or more application servers.

Assignees

• Appdynamics Inc

Inventors

• Carmel Ido
• Sawant Abhijit
• Singh Raghvendra
• Arai Takashi
• Morgan Andrew
• Sunkara Bhaskar

Classifications

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F2201/87

  Monitoring of transactions · CPC title

• G06F11/0793 Primary

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• G06F11/3409

  for performance assessment · CPC title

• G06F11/3495

  for systems · CPC title