Multi-tenant java agent instrumentation system
In one embodiment, a device launches a core agent for a Java application. The core agent loads a first tenant and a second tenant, each tenant having its own isolated class loader. The device instruments, via the core agent and by each tenant, the Java application to capture data regarding execution of the Java application. The device provides the captured data to a user interface.
1. A method, comprising:
launching, by a device, a core agent for a Java application comprising an agent loader that is a parent for class loaders of tenants;
creating, by the core agent, tenant modules for a first tenant and a second tenant of the tenants, the tenant modules readable by a module of the Java application;
loading, by the core agent, the first tenant and the second tenant such that the first tenant and the second tenant each have respective isolated class loaders that do not conflict with one another or the Java application;
instrumenting, via the core agent, the Java application to capture data regarding execution of the Java application according to requirements of the first tenant and the second tenant; and
providing the captured data to a user interface,
wherein launching the core agent for the Java application comprises:
setting, by the agent loader, the tenant modules to be able to export to at least one of: a boot module or a premain module of the Java application; and
setting, by the agent loader, the tenant modules to be readable by at least one of:
the boot module or the premain module of the Java application.
2. The method as in claim 1 , wherein the first tenant is an application performance management (APM) tenant that instruments the Java application to collect performance data regarding the Java application.
3. The method as in claim 2 , wherein the second tenant is a Runtime Application Self Protection (RASP) tenant that instruments the Java application to monitor the Java application for signs of malicious activity.
4. The method as in claim 1 , wherein the core agent is launched using a premain method.
5. The method as in claim 1 , wherein instrumenting, via the core agent and by each tenant, the Java application to capture the data regarding execution of the Java application comprises:
using a handler to capture at least one of: an object instance, one or more arguments, or a return value of a method of the Java application.
6. The method as in claim 1 , wherein instrumenting, via the core agent and by each tenant, the Java application to capture the data regarding execution of the Java application comprises:
instrumenting an anonymous class of the Java application.
7. The method as in claim 1 , wherein launching the core agent for the Java application comprises:
launching the core agent as a Java agent.
8. The method as in claim 1 , wherein each tenant comprises a configuration file that defines a handler to instrument the Java application.
9. A tangible, non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by a processor on a device, cause the device to perform a method comprising:
launching, by the device, a core agent for a Java application comprising an agent loader that is a parent for class loaders of respective tenants;
creating, by the core agent, tenant modules for a first tenant and a second tenant of the tenants, the tenant modules readable by a module of the Java application;
loading, by the core agent, the first tenant and the second tenant such that the first tenant and the second tenant each have respective isolated class loaders that do not conflict with one another or the Java application;
instrumenting, via the core agent, the Java application to capture data regarding execution of the Java application according to requirements of the first tenant and the second tenant; and
providing the captured data to a user interface,
wherein launching the core agent for the Java application comprises:
setting, by the agent loader, the tenant modules to be able to export to at least one of: a boot module or a premain module of the Java application; and
setting, by the agent loader, the tenant modules to be readable by at least one of:
the boot module or the premain module of the Java application.
10. The computer-readable medium as in claim 9 , wherein the first tenant is an application performance management (APM) tenant that instruments the Java application to collect performance data regarding the Java application.
11. The computer-readable medium as in claim 10 , wherein the second tenant is a Runtime Application Self Protection (RASP) tenant that instruments the Java application to monitor the Java application for signs of malicious activity.
12. The computer-readable medium as in claim 9 , wherein instrumenting, via the core agent and by each tenant, the Java application to capture the data regarding execution of the Java application comprises:
using a handler to capture at least one of: an object instance, one or more arguments, or a return value of a method of the Java application.
13. The computer-readable medium as in claim 9 , wherein instrumenting, via the core agent and by each tenant, the Java application to capture the data regarding execution of the Java application comprises:
instrumenting an anonymous class of the Java application.
14. The computer-readable medium as in claim 9 , wherein each tenant comprises a configuration file that defines a handler to instrument the Java application.
15. An apparatus, comprising:
one or more network interfaces to communicate with a network;
a processor coupled to the network interfaces and configured to execute one or more processes; and
a memory configured to store a process executable by the processor, the process, when executed, configured to:
launch a core agent for a Java application comprising an agent loader that is a parent for class loaders of tenants;
create, by the core agent, tenant modules for a first tenant and a second tenant of the tenants, the tenant modules readable by a module of the Java application;
load the first tenant and the second tenant, by the core agent, such that the first tenant and the second tenant each have respective isolated class loaders that do not conflict with one another or the Java application;
instrument, via the core agent, the Java application to capture data regarding execution of the Java application according to requirements of the first tenant and the second tenant; and
provide the captured data to a user interface,
wherein the apparatus launches the core agent for the Java application by:
setting, by the agent loader, the tenant modules to be able to export to at least one of: a boot module or a premain module of the Java application; and
setting, by the agent loader, the tenant modules to be readable by at least one of: the boot module or the premain module of the Java application.