# US 2026/0099426 A1 · Dynamic instrumentation for software applications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099426 A1
- Document ID: US20260099426A1
- Status: Published application
- Kind: A1
- Application number: 18/799,162
- Filed: 2024-08-09
- Published: 2026-04-09
- Earliest claimed: 2024-08-09
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Rahul Singh; Ashutosh Goel; Sanket Nalinkant Mehta
- Web page: https://patentgrep.com/patent/US20260099426A1

## CPC

- G06F 11/302: {where the computing system component is a software system}
- G06F 11/3616: {using software metrics}
- G06F 11/3093: {Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 11/3644: {by instrumenting at runtime}
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques are provided for injecting dynamic instrumentation to software applications. A method includes a telemetry agent initiating an observability session with a software application and altering an import statement of the software application to generate one or more proxy objects. The method further includes the telemetry agent determining one or more instrumentations based on a configuration file for the observability session and instantiating the one or more instrumentations in the software application using the one or more proxy objects.

## Claims

### Claim 1

A computer-implemented method comprising:
initiating, by a telemetry agent, an observability session with a software application;
altering, by the telemetry agent, an import statement of the software application to generate one or more proxy objects;
determining, by the telemetry agent, one or more instrumentations based on a configuration file for the observability session; and
instantiating, by the telemetry agent, the one or more instrumentations in the software application using the one or more proxy objects.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the observability session is initiated by injecting a script to the software application on bootup.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein instantiating further comprises:
inserting the one or more instrumentations into the software application using the one or more proxy objects; and
capturing telemetry data associated with the software application in response to the one or more instrumentations.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the import statement is one of a direct import statement or an indirect import statement.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, wherein the one or more proxy objects mimic one or more behaviors of one or more original objects of the software application.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the configuration file is configured to store one or more of: a module name, a method name, or one or more metrics to be tracked by the one or more instrumentations.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1, wherein the configuration file is received from one or more of: a file system, a database, a server, a user, or an intermediary between the telemetry agent and a controller.

### Claim 8

An apparatus comprising:
a network interface that enables network communications;
a memory; and
one or more processors coupled to the network interface and the memory, wherein the one or more processors are configured to perform operations including:
initiating an observability session with a software application;
altering an import statement of the software application to generate one or more proxy objects;
determining one or more instrumentations based on a configuration file for the observability session; and
instantiating the one or more instrumentations in the software application using the one or more proxy objects.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the observability session is initiated by injecting a script to the software application on bootup.

### Claim 10 (depends on 8)

The apparatus of claim 8, wherein instantiating further comprises:
inserting the one or more instrumentations into the software application using the one or more proxy objects; and
capturing telemetry data associated with the software application in response to the one or more instrumentations.

### Claim 11 (depends on 8)

The apparatus of claim 8, wherein the import statement is one of a direct import statement or an indirect import statement.

### Claim 12 (depends on 8)

The apparatus of claim 8, wherein the one or more proxy objects mimic one or more behaviors of one or more original objects of the software application.

### Claim 13 (depends on 8)

The apparatus of claim 8, wherein the configuration file is configured to store one or more of: a module name, a method name, or one or more metrics to be tracked by the one or more instrumentations.

### Claim 14 (depends on 8)

The apparatus of claim 8, wherein the configuration file is received from one or more of: a file system, a database, a server, a user, or an intermediary between a telemetry agent and a controller.

### Claim 15

One or more non-transitory computer readable storage media encoded with instructions that, when executed by a processor, cause the processor to:
initiate an observability session with a software application;
alter an import statement of the software application to generate one or more proxy objects;
determine one or more instrumentations based on a configuration file for the observability session; and
instantiate the one or more instrumentations in the software application using the one or more proxy objects.

### Claim 16 (depends on 15)

The one or more non-transitory computer readable storage media of claim 15,
wherein the observability session is initiated by injecting a script to the software application on bootup.

### Claim 17 (depends on 15)

The one or more non-transitory computer readable storage media of claim 15, wherein the instructions are operable to cause the processor to instantiate the one or more instrumentations in the software application using the one or more proxy objects by:
inserting the one or more instrumentations into the software application using the one or more proxy objects; and
capturing telemetry data associated with the software application in response to the one or more instrumentations.

### Claim 18 (depends on 15)

The one or more non-transitory computer readable storage media of claim 15, wherein the import statement is one of a direct import statement or an indirect import statement.

### Claim 19 (depends on 15)

The one or more non-transitory computer readable storage media of claim 15, wherein the one or more proxy objects mimic one or more behaviors of one or more original objects of the software application.

### Claim 20 (depends on 15)

The one or more non-transitory computer readable storage media of claim 15, wherein the configuration file is configured to store one or more of: a module name, a method name, or one or more metrics to be tracked by the one or more instrumentations, and wherein the configuration file is received from one or more of: a file system, a database, a server, a user, or an intermediary between a telemetry agent and a controller.
