Agent dynamic service
A dynamic service module is embedded in an agent and able to add functionality to the agent. The service module may manage .jar files for execution by the agent. The service module may receive the .jar files, provide them to an agent for execution, and may perform other functions. The agent may perform obfuscation in order to translate the .jar files into a modified version which may be more compatible with a particular agent. Once execution of the .jar file is complete, the agent may remove the .jar file as well as all trace of the .jar file. For example, the agent may remove byte code instrumentation that was installed as a result of the .jar file.
1. A method for monitoring an application, comprising:
receiving a first .jar file by an agent within an application on a server;
creating a new .jar file from the received .jar file, wherein the new .jar file modifies references to agent elements found in the received .jar file including at least references to agent class, methods and fields;
running the new .jar file, wherein the new .jar file is placed in a .jar file directory; and
removing the .jar file and code created by the .jar file by a service module by removing the executed new .jar file from the .jar file directory, and removing traces of the new .jar file by removing byte instrumented code generated as a result of running the new .jar file.
2. The method of claim 1 , wherein the new .jar file is created by an obfuscation adaptor.
3. The method of claim 1 , wherein creating the new .jar file includes using one or more keys that indicate the modified references to agent elements found in the received .jar file.
4. The method of claim 1 , further comprising:
performing, by the agent, a functionality in response to running the new .jar file.
5. The method of claim 4 , the received .jar file is indicative of the functionality to be performed by the agent.
6. The method of claim 5 , wherein the functionality performed by the agent include generating a generic interceptor insertion, specifying match conditions, tracing I/O activity over network sockets, scanning threads for activity, or locating and examining class loaders.
7. The non-transitory computer readable storage medium of claim 5 , wherein the functionality performed by the agent include generating a generic interceptor insertion, specifying match conditions, tracing I/O activity over network sockets, scanning threads for activity, or locating and examining class loaders.
8. The method of claim 4 , the received .jar file is indicative of the functionality to be performed by the agent.
9. The method of claim 1 , wherein receiving the .jar file includes receiving the .jar file from a remote server.
10. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for monitoring an application, the method comprising:
receiving a first .jar file by an agent within an application on a server;
creating a new .jar file from the received .jar file, wherein the new .jar file modifies references to agent elements found in the received .jar file including at least references to agent class, methods and fields;
running the new .jar file, wherein the new .jar file is placed in a .jar file directory; and
removing the .jar file and code created by the .jar file by a service module by removing the executed new .jar file from the .jar file directory, and removing traces of the new .jar file by removing byte instrumented code generated as a result of running the new .jar file.
11. The non-transitory computer readable storage medium of claim 10 , wherein the new .jar file is created by an obfuscation adaptor.
12. The non-transitory computer readable storage medium of claim 10 , wherein creating the new .jar file includes using one or more keys that indicate the modified references to agent elements found in the received .jar file.
13. The non-transitory computer readable storage medium of claim 10 , the method further comprising:
performing, by the agent, a functionality in response to running the new .jar file.
14. A system for monitoring an application, comprising:
a processor;
a memory; and
one or more modules stored in memory and executable by a processor to receive a first .jar file by an agent within an application on a server, create a new .jar file from the received .jar file, wherein the new .jar file modifies references to agent elements found in the received .jar file including at least references to agent class, methods and fields, run the new .jar file, wherein the new .jar file is placed in a .jar file directory, and remove the .jar file and code created by the .jar file by a service module by removing the executed new .jar file from the .jar file directory, and removing traces of the new .jar file by removing byte instrumented code generated as a result of running the new .jar file.
15. The system of claim 14 , wherein the new .jar file is created by an obfuscation adaptor.
16. The system of claim 14 , wherein creating the new .jar file includes using one or more keys that indicate the modified references to agent elements found in the received .jar file.