Granted Patent B2

US 12,360,776 · App. 18/122,004 · Granted Jul 15, 2025

Inventor: Walter Theodore Hulick, Jr. (Pearland, TX)

Assignee: Cisco Technology, Inc.

G06F9/445G06F8/315G06F9/44521G06F11/3409G06F11/3466G06F11/3616G06F21/51G06F21/57

Abstract

Claims (45)

1. A method, comprising:

launching, by a device, a core agent, for a Java application, that comprises an agent loader;

creating, by the core agent, tenant modules for a first tenant and a second tenant of tenants, wherein the agent loader sets the tenant modules to be readable by one or more modules of the Java application;

loading, by the core agent, the first tenant having a first isolated class loader and the second tenant having a second isolated class loader, wherein the agent loader is a parent for the first isolated class loader and the second isolated class loader;

instrumenting, via the core agent and by each tenant, the Java application to capture data regarding execution of the Java application; and

providing the data regarding execution of the Java application to a user interface.

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, by a device, the core agent for a 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.

8. The method as in claim 1 , wherein launching the core agent for the Java application comprises:

launching the core agent as a Java agent.

9. The method as in claim 1 , wherein each tenant comprises a configuration file that defines a handler to instrument the Java application.

10. 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, that comprises an agent loader;

creating, by the core agent, tenant modules for a first tenant and a second tenant of tenants, wherein the agent loader sets the tenant modules to be readable by one or more modules of the Java application;

loading, by the core agent, the first tenant having a first isolated class loader and the second tenant having a second isolated class loader, wherein the agent loader is a parent for the first isolated class loader and the second isolated class loader;

instrumenting, via the core agent and by each tenant, the Java application to capture data regarding execution of the Java application; and

providing the data regarding execution of the Java application to a user interface.

11. The computer-readable medium as in claim 10 , wherein the first tenant is an application performance management (APM) tenant that instruments the Java application to collect performance data regarding the Java application.

12. The computer-readable medium as in claim 11 , 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.

13. The computer-readable medium as in claim 10 , 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.

14. The computer-readable medium as in claim 10 , wherein launching, by a device, the core agent for a 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.

15. The computer-readable medium as in claim 10 , 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.

16. The computer-readable medium as in claim 10 , wherein each tenant comprises a configuration file that defines a handler to instrument the Java application.

17. The computer-readable medium as in claim 10 , wherein the core agent is launched using a premain method.

18. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the one or more 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, that comprises an agent loader;

create, by the core agent, tenant modules for a first tenant and a second tenant of tenants, wherein the agent loader sets the tenant modules to be readable by one or more modules of the Java application;

load the first tenant having a first isolated class loader and the second tenant having a second isolated class loader, by the core agent, wherein the agent loader is a parent for the first isolated class loader and the second isolated class loader;

instrument, via the core agent and by each tenant, the Java application to capture data regarding execution of the Java application; and

provide the data regarding execution of the Java application to a user interface.

Assignments (1)

Continuity (2)

References Cited (31)