Method and system for deployment of agents
View Patent ↗Systems and methods for deploying agents for a management system across IT infrastructure in an automated fashion are disclosed herein. Embodiments of the present invention allow agents to be substantially automatically deployed or configured in conjunction with previously unknown or newly added application components. More specifically, embodiments of the present invention may track traffic associated with application components to identify unknown application components. Agents may then be deployed to monitor these newly identified application components.
1. A method executed on processor in a management server in a network for deploying monitoring agents in the network, comprising:
deploying a first agent to monitor a first application component of an application,
wherein the first agent is operable to monitor a communication associated with the first application component, wherein the communication is outbound from the first application component to an unknown second application component of the application;
determining if the communication is associated with the unknown second application component of the application where the unknown second application component is not monitored, including analyzing the communication to determine if the communication comprises a correlator;
determining an identifier for a type of the unknown second application component and a location for the unknown second application component based on the communication, wherein the type of the unknown second application component is determined by analyzing a protocol of the communication;
if the communication is associated with the unknown second application component, deploying a second agent over the network to monitor the unknown second application component, wherein the second agent is selected based on the identifier and the location of the unknown second application component; and
assembling a deployment candidate list comprising the identifier for the type of the unknown second application component and the location of the unknown second application component.
2. The method of claim 1 , wherein determining if the communication is associated with the unknown second application component comprises determining a location of the unknown second application component and comparing the location to a list of known application components.
3. The method of claim 1 , further comprising receiving the deployment candidate list at a management application, wherein the second agent is deployed to monitor the unknown second application component from the management application.
4. The method of claim 3 , wherein the second agent deployed is determined based on the type of the unknown second application component.
5. The method of claim 4 , wherein the deployment candidate list is reviewed by a user before the second agent is deployed.
6. The method of claim 1 , further comprising determining if the first application component has not been utilized for a period of time and uninstalling the first agent if the first application component has not been utilized for the period of time.
7. A non-transitory computer readable medium, comprising instructions translatable for deploying monitoring agents from a management server in a network:
deploying a first agent to monitor a first application component of an application, wherein the first agent is operable to monitor a communication associated with the first application component, wherein the communication is outbound from the first application component to an unknown second application component of the application;
determining if the communication is associated with the unknown second application component of the application where the unknown second application component is not monitored, including analyzing the communication to determine if the communication comprises a correlator;
determining an identifier for a type of the unknown second application component and a location for the unknown second application component based on the communication, wherein the type of the unknown second application component is determined by analyzing a protocol of the communication; and
if the communication is associated with the unknown second application component, deploying a second agent over the network to monitor the unknown second application component, wherein the second agent is selected based on the identifier and the location of the unknown second application component; and
assembling a deployment candidate list comprising the identifier for the type of the second application component and the location of the second application component.
8. The non-transitory computer readable medium of claim 7 , wherein determining if the communication is associated with the second application component comprises determining a location of the second application component and comparing the location to a list of known application components.
9. The non-transitory computer readable medium of claim 7 , wherein the instructions are further translatable for receiving the deployment candidate list at a management application, wherein the second agent is deployed to monitor the second application component from the management application.
10. The non-transitory computer readable medium of claim 9 , wherein the second agent deployed is determined based on the type of the second application component.
11. The non-transitory computer readable medium of claim 10 , wherein the deployment candidate list is reviewed by a user before the second agent is deployed.
12. The non-transitory computer readable medium of claim 7 , wherein the instructions are further translatable for determining if the first application component has not been utilized for a period of time and uninstalling the first agent if the first application component has not been utilized for the period of time.
13. A management system, comprising:
a set of servers, wherein each server has a processor;
a management server coupled to the set of servers through a network, wherein the management server has a processor;
a first set of agents, each of the agents on one of the set of servers and operable to assemble a list of unknown application components by monitoring a communication to an application component and
determine if the communication is associated with an unknown application component by analyzing the communication to determine if the communication comprises a correlator,
wherein the list of unknown application components includes a location and a type of each unknown application component, where the location and type were determined based on the communication, wherein the type of the unknown application component is determined by analyzing a protocol of the communication; and
a management application on the management server operable to receive the lists of unknown application components from the set of agents and deploy a second set of agents to a set of the unknown application components over the network based on the location and the type of the set of the unknown application components, each of the second set of agents operable to monitor a corresponding unknown application component.
14. The management system of claim 13 , wherein each of the first set of agents maintains a list of known application components and each of the first set of agents is operable to compare a destination of the communication with the list of known application components to determine if the communication is associated with an unknown application component.
15. The management system of claim 13 , wherein the manager application is operable to determine the type of each of the set of second agents based on the type of the second application component.
16. The management system of claim 13 , wherein the unknown application components in the lists of unknown application components are reviewed by a user such that the user can select the set of unknown application components on which the second set of agents are deployed.