System and method for managing configuration data of monitoring agents

1. A computer implemented method comprising:

determining an application to be monitored in an endpoint;

generating a marker with a unique identifier corresponding to the application running in the endpoint;

bundling configuration data within the marker by inserting the configuration data between a start marker and an end marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

appending the marker bundled with the configuration data to a configuration file of the monitoring agent, wherein the marker is to distinguish the configuration data of the application from configuration data of other applications, that are being monitored by the monitoring agent, in the configuration file;

enabling the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier; and

disabling monitoring of the application comprising:

determining the unique identifier for the application running in the endpoint; and

disabling monitoring of the application by deleting the configuration data within the marker that is associated with the unique identifier.

2. A computer implemented method comprising:

determining an application to be monitored in an endpoint;

generating a marker with a unique identifier corresponding to the application running in the endpoint;

bundling configuration data within the marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

appending the marker bundled with the configuration data to a configuration file of the monitoring agent;

enabling the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier; and

disabling monitoring of the application, wherein disabling the monitoring of the application comprises:

determining the unique identifier for the application running in the endpoint;

recreating a reference marker using the unique identifier to identify the application;

matching the reference marker with the marker stored in the configuration file; and

deleting the configuration data within the marker that matches the reference marker to disable monitoring of the application.

3. A computer implemented method comprising:

determining an application to be monitored in an endpoint;

generating a marker with a unique identifier corresponding to the application running in the endpoint;

bundling configuration data within the marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

appending the marker bundled with the configuration data to a configuration file of the monitoring agent;

enabling the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier;

receiving a checksum of the configuration data of the application being monitored from the endpoint via a network;

comparing the received checksum to a versioning file stored in an application monitoring server, wherein the versioning file comprises checksums of configuration data of multiple applications obtained from static content hosted in the application monitoring server, and wherein the checksums are dynamically updated upon performing updates to the static content on the application monitoring server;

determining an update to the configuration data of the application in the endpoint based on the comparison;

sending the update to the endpoint via the network; and

updating the configuration data within the marker in response to a user selection of the update.

4. The computer implemented method of claim 1 , further comprising:

receiving input data associated with the application from a user; and

generating the configuration data using the received input data.

5. The computer implemented method of claim 1 , wherein the unique identifier comprises any combination of application name, port number, and service identifier associated with the application.

6. A computer implemented method comprising:

determining an application to be monitored in an endpoint;

generating a marker with a unique identifier corresponding to the application running in the endpoint;

bundling configuration data within the marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

appending the marker bundled with the configuration data to a configuration file of the monitoring agent, wherein appending the marker bundled with the configuration data to the configuration file comprises:

decrypting the configuration file of the monitoring agent running in the endpoint upon receiving a request to monitor the application, the configuration file comprising the configuration data of the monitoring agent to monitor the application;

appending the marker bundled with the configuration data to the decrypted configuration file; and

encrypting the configuration file including the marker bundled with the configuration data; and

enabling the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier.

7. The computer implemented method of claim 1 , wherein determining the application to be monitored comprises determining the application to be monitored in response to receiving a request to monitor the application.

8. The computer implemented method of claim 1 , further comprising:

encrypting at least a portion of the configuration file including the configuration data bundled within the marker upon executing the monitoring agent.

9. A system comprising:

an endpoint having a monitoring agent to monitor applications running therein; and

an application monitoring server communicatively connected to the endpoint via a network, wherein the application monitoring server comprises an agent monitoring unit to:

determine an application to be monitored, the application running in the endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker by inserting the configuration data between a start marker and an end marker, wherein the configuration data is to specify a configuration for the monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent, wherein the marker is to distinguish the configuration data of the application from configuration data of other applications, that are being monitored by the monitoring agent, in the configuration file;

instruct the monitoring agent to monitor the application according to the configuration data in the configuration file and the unique identifier; and

disable monitoring of the application by:

determining the unique identifier for the application running in the endpoint; and

disabling monitoring of the application by deleting the configuration data within the marker that is associated with the unique identifier.

10. A system comprising:

an endpoint having a monitoring agent to monitor applications running therein; and

an application monitoring server communicatively connected to the endpoint via a network, wherein the application monitoring server comprises an agent monitoring unit to:

determine an application to be monitored, the application running in the endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker, wherein the configuration data is to specify a configuration for the monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent;

instruct the monitoring agent to monitor the application according to the configuration data in the configuration file and the unique identifier; and

disable the monitoring of the application by:

determining the unique identifier for the application running in the endpoint;

recreating a reference marker using the unique identifier to identify the application;

matching the reference marker with the marker stored in the configuration file; and

deleting the configuration data within the marker that matches the reference marker.

11. A system comprising:

an endpoint having a monitoring agent to monitor applications running therein; and

an application monitoring server communicatively connected to the endpoint via a network, wherein the application monitoring server comprises an agent monitoring unit to:

determine an application to be monitored, the application running in the endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker, wherein the configuration data is to specify a configuration for the monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent;

instruct the monitoring agent to monitor the application according to the configuration data in the configuration file and the unique identifier;

receive a checksum of the configuration data of the application being monitored from the endpoint via a network;

compare the received checksum to a versioning file stored in the application monitoring server, wherein the versioning file comprises checksums of configuration data of multiple applications obtained from static content hosted in the application monitoring server, and wherein the checksums are dynamically updated upon performing updates to the static content on the application monitoring server;

determine an update to the configuration data of the application in the endpoint based on the comparison;

send the update to the endpoint via the network; and

update the configuration data within the marker in response to a user selection of the update.

12. The system of claim 9 , wherein the agent monitoring unit is to:

receive, via a user interface, input data associated with the application from a user; and

generate the configuration data using the received input data.

13. The system of claim 9 , wherein the unique identifier comprises any combination of application name, port number, and service identifier associated with the application.

14. A system comprising:

an endpoint having a monitoring agent to monitor applications running therein; and

an application monitoring server communicatively connected to the endpoint via a network, wherein the application monitoring server comprises an agent monitoring unit to:

determine an application to be monitored, the application running in the endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker, wherein the configuration data is to specify a configuration for the monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent by:

decrypting the configuration file of the monitoring agent running in the endpoint upon receiving a request to monitor the application, the configuration file comprising the configuration data of the monitoring agent to monitor the application;

bundling the configuration data corresponding to the application within the marker;

appending the marker bundled with the configuration data to the decrypted configuration file; and

encrypting the configuration file including the marker bundled with the configuration data; and

instruct the monitoring agent to monitor the application according to the configuration data in the configuration file and the unique identifier.

15. A non-transitory machine-readable storage medium encoded with instructions that, when executed by a computer, cause the computer to:

determine an application to be monitored in an endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker by inserting the configuration data between a start marker and an end marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent, wherein the marker is to distinguish the configuration data of the application from configuration data of other applications, that are being monitored by the monitoring agent, in the configuration file;

enable the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier; and

disable monitoring of the application by:

determining the unique identifier for the application running in the endpoint; and

disabling monitoring of the application by deleting the configuration data within the marker that is associated with the unique identifier.

16. A non-transitory machine-readable storage medium encoded with instructions that, when executed by a computer, cause the computer to:

determine an application to be monitored in an endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent;

enable the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier; and

disable monitoring of the application, wherein instructions to disable monitoring of the application comprise instructions to:

determine the unique identifier for the application running in the endpoint;

recreate a reference marker using the unique identifier to identify the application;

match the reference marker with the marker stored in the configuration file; and

delete the configuration data within the marker that matches the reference marker to disable monitoring of the application.

17. A non-transitory machine-readable storage medium encoded with instructions that, when executed by a computer, cause the computer to:

determine an application to be monitored in an endpoint;

generate a marker with a unique identifier corresponding to the application running in the endpoint;

bundle configuration data within the marker, wherein the configuration data is to specify a configuration for a monitoring agent installed on the endpoint to monitor the application;

append the marker bundled with the configuration data to a configuration file of the monitoring agent;

enable the monitoring agent to monitor the application based on the configuration data in the configuration file and the unique identifier;

receive a checksum of the configuration data of the application being monitored from the endpoint via a network;

compare the received checksum to a versioning file stored in the computer, wherein the versioning file comprises checksums of configuration data of multiple applications obtained from static content hosted in the computer, and wherein the checksums are dynamically updated upon performing updates to the static content on the computer;

determine an update to the configuration data of the application in the endpoint based on the comparison;

send the update to the endpoint via the network; and

update the configuration data within the marker in response to a user selection of the update.

18. The non-transitory machine-readable storage medium of claim 15 , wherein the unique identifier comprises any combination of application name, port number, and service identifier associated with the application.