# US 2022/0046076 A1 · Method And System For Real-Time Modeling Of Communication, Virtualization And Transaction Execution Related Topological Aspects Of Monitored Software Applications And Hardware Entities

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

- Number: US 2022/0046076 A1
- Document ID: US20220046076A1
- Status: Published application
- Kind: A1
- Application number: 17/508,313
- Filed: 2021-10-22
- Published: 2022-02-10
- Earliest claimed: 2014-10-10
- Assignees: Dynatrace LLC
- Applicants: Dynatrace LLC
- Inventors: Bernd GREIFENEDER; Ernst AMBICHL; Andreas LEHOFER; Gunther SCHWARZBAUER; Helmut SPIEGL; Rafal MLOTOWSKI
- Web page: https://patentgrep.com/patent/US20220046076A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/12: Discovery or management of network topologies
- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 41/5058: {Service discovery by the service manager}
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/62: Establishing a time schedule for servicing the requests
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for real-time discovery and monitoring of multidimensional topology models describing structural aspects of applications and of computing infrastructure used to execute those applications is disclosed. Different types of agents are deployed to the monitored application execution infrastructure dedicated to capture specific topological aspects of the monitored system. Virtualization agents detect and monitor the virtualization structure of virtualized hardware used in the execution infrastructure, operating system agents deployed to individual operating systems monitor resource utilization, performance and communication of processes executed by the operating system and transaction agents deployed to processes participating in the execution of transactions, providing end-to-end transaction trace and monitoring data describing individual transaction executions. The monitoring and tracing data of the deployed agents contains correlation data that allows to create a topology model of the monitored system that integrates transaction execution, process execution and communication and virtualization related aspects.

## Claims

### Claim at position 1

-30. (canceled)

### Claim 31

A computer-implemented method for monitoring a distributed transaction by a monitoring system across a distributed computing environment, comprising:
receiving, by a transaction agent, transaction trace data that identifies a transaction being executed in part on a host computing device, where the transaction trace data includes an identifier for a thread executed by a process and the transaction agent is instrumented in the process;
identifying, by a service sensor instrumented in a method executed by the process, a service used by the transaction to enter the process, where the service is executed in the process and the identification of the service occurs in response to the method receiving a request;
receiving, by the transaction agent, service data from the service sensor, where the service data contains data identifying the service used by the transaction to enter the process;
retrieving, by the transaction agent, process group information identifying a process group to which the process belongs and operating system information identifying an operating system executing on the host computing device and upon which the process is running;
sending, by the transaction agent, the transaction trace, data, the service data, the process group information and the operation system information over a network to a monitoring node located remotely from the host computing device;
receiving, by a topology processor residing on the monitoring node, the transaction trace data, the service data, the process group information and the operating system information; and
creating, by the topology processor, an update for a topology repository, where the update for the topology repository includes creating a topology entity for at least one of the service, the process group and the operating system.

### Claim 32 (depends on 31)

The computer-implemented method for claim 31 further comprises receiving the transaction trace data and the service data from the service sensor instrumented in the method, where the method is configured to receive a request from another process.

### Claim 33 (depends on 32)

The computer-implemented method of claim 32 further comprises receiving a service request for the service and parsing the service request to determine the service data, where the service request includes a uniform resource locator (URL).

### Claim 34 (depends on 33)

The computer-implemented method of claim 33 wherein the service data includes an identifier for a server computer and an identifier for a protocol for accessing the server computer.

### Claim 35 (depends on 31)

The computer-implemented method of claim 31 further comprises
determining, by an OS agent, metadata for the process and metadata for the operating system, where the OS agent is running on the host computing device;
sending, by the OS agent, an OS topology event over the network to the monitoring node, where the OS topology event includes the metadata for the process and the operating system; and
correlating, by a topology processor, the trace and topology correlation data with the metadata for the process and the operating system, where the topology processor resides on the monitoring node.

### Claim 36 (depends on 33)

The computer-implemented method of claim 33 further comprises determining, by the topology processor, a vertical relationship between a method servicing a service request and the service from the service data and creating a record in the topology repository for the vertical relationship, where the topology processor resides on the monitoring node.

### Claim 37 (depends on 36)

The computer-implemented method of claim 36 wherein the service is further defined as a remote method invocation (RMI) service, and the method is further defined as a specific remote method which is provided by the RMI service for remote execution.

### Claim 38 (depends on 33)

The computer-implemented method of claim 33 further comprises determining, by the topology processor, a vertical relationship between the service used by the transaction to enter the process and the process group to which the process belongs.

### Claim 39 (depends on 33)

The computer-implemented method of claim 33 further comprises determining, by a topology processor, a horizontal relationship between the service servicing the service request and another service called by the service from the service data and creating a record in a topology repository for the horizontal relationship, where the topology processor resides on the monitoring node.

### Claim 40 (depends on 31)

The computer-implemented method of claim 31 wherein the transaction agent interacts with an OS agent to determine the identifying information for a process group to which the process belongs and identifying information for an operating system upon which the process is running, where the OS agent is running on the host computing device.

### Claim 41 (depends on 40)

The computer-implemented method of claim 40 further comprises extracting, by the OS agent, process group information identifying the process group from at least one of process metadata or from a command which initiates the process.

### Claim 42 (depends on 31)

The computer-implemented method of claim 31 wherein processes having the similar functions are mapped to the same process group.

### Claim 43 (depends on 31)

The computer-implemented method of claim 31 further comprises
determining, by an OS agent, metadata for a given process and metadata for the operating system, where the given process is running on the host computing device and the OS agent is running on the host computing device;
detecting, by the OS agent, a communication with another process running on a second operating system on a second host device, where the given process is participating in the communication; and
sending, by the OS agent, a communication topology event over the network to the monitoring node, where the communication topology event includes information identifying a process group to which the given process belongs, information identifying the operating system, a network address and port identifier for host computing device and a network address and port identifier for the second host device.

### Claim 44 (depends on 43)

The computer-implemented method of claim 43 further comprises
receiving, by a topology processor, the communication topology event from the host computing device, where the topology processor resides on the monitoring node;
receiving, by the topology processor, a second communication topology event from the second host device, where the second communication topology event includes information identifying a second process group to which the another process belongs, information identifying the second operating system, the network address and port identifier for the host computing device and the network address and port identifier for the second host device;
determining, by the topology processor, a horizontal relationship between the process group of the given process and the second process group of the another process using the communication topology event and the second communication topology event; and
creating a record for the horizontal relationship in a topology repository.

### Claim 45 (depends on 43)

The computer-implemented method of claim 43 further comprises
sending, by the OS agent, an OS topology event over the network to the monitoring node, where the OS topology event includes metadata for the given process and the operating system and where the metadata for the given process includes information identifying a process group to which the given process belongs;
determining, by a topology processor, a vertical relationship between the operating system and the process group to which the given process belongs using the OS topology event; and
creating a record for the vertical relationship in a topology repository.

### Claim 46 (depends on 31)

The computer-implemented method of claim 31 further comprises
detecting, by a virtualization agent, other host computing devices implemented as virtualized computer systems;
generating, by the virtualization agent, a virtualization topology event for the detected virtualized computer systems, where the virtualization topology event includes data identifying the virtualized computer system and an identifier for a network interface assigned to the virtualized computer system;
sending, by the virtualization agent, the virtualization topology event over a network to a monitoring node located remotely from the host device;
determining, by an OS agent, information identifying an operating system running on a particular one of the other host computing devices, wherein the OS agent is running on the operating system;
generating, by the OS agent, an OS topology event, where the OS topology event includes data identifying the operating system and the identifier for a network interface assigned to the host computing device;
sending, by the OS agent, the OS topology event over the network to the monitoring node; and
correlating, by a topology processor, the particular one of the other host computing devices with the virtualized computer system using the identifier for the network interface of the virtualized computer system and the identifier for the network interface assigned to the host computing device, where the topology processor resides on the monitoring node.

### Claim 47

A computer-implemented system for monitoring a distributed transaction across a distributed computing environment, comprising:
a transaction agent instrumented in a process executing on a host computing device and executed by a processor of the host computing device, the transaction agent is configured to receive transaction trace data that identifies a transaction being executed in part on the host computing device and the transaction trace data includes an identifier for a thread executing the transaction;
a service sensor instrumented in a method executed by the process, wherein the service sensor operates to identify the service used by the transaction to enter the process and sends service data to the transaction agent, where the service is executed in the process, the service data identifies the service used by the transaction to enter the process, and the identification of the service occurs in response to the method receiving a request; and
an OS agent running on the host computing device and executed by the processor of the host computing device, the OS agent determines information identifying a process group to which the process belongs and information identifying an operating system executing on the host computing device and upon which the process is running and communicates the information for the process group and information for the operating system to the transaction agent;
wherein the transaction agent sends the transaction trace data and the service data with the information for the process group and the operating system over a network to a monitoring node located remotely from the host computing device.

### Claim 48 (depends on 47)

The computer-implemented system of claim 47 further comprises the service sensor instrumented in the method associated with the service, the service sensor determines the transaction trace data and the service data and sends the transaction trace data and the service data to the transaction agent, wherein the service data includes an identifier for a server computer and an identifier for a protocol for accessing the server computer.

### Claim 49 (depends on 48)

The computer-implemented system of claim 48 wherein the OS agent determines metadata for the process and metadata for the operating system and sends an OS topology event over the network to the monitoring node, where the OS topology event includes the metadata for the process, metadata for the operating system and the identifying information for a process group to which the process belongs.

### Claim 50 (depends on 49)

The computer-implemented system of claim 49 further comprises a topology processor residing on the monitoring node and configured to receive the trace and topology correlation data, the topology processor determines from the trace and topology correlation data a vertical relationship between a method servicing a service request and the service and creates a record in a topology repository for the vertical relationship.

### Claim 51 (depends on 49)

The computer-implemented system of claim 49 further comprises a topology processor residing on the monitoring mode and configured to receive the trace and topology correlation data, the topology processor determines from the trace and topology correlation data a vertical relationship between the service used by the transaction to enter the process and the process group to which the process belongs.

### Claim 52 (depends on 49)

The computer-implemented system of claim 49 further comprises a topology processor residing on the monitoring mode and configured to receive the trace and topology correlation data, the topology processor determines from the trace and topology correlation data a horizontal relationship between the service and another service called by the service and creating a record in a topology repository for the horizontal relationship.

### Claim 53 (depends on 49)

The computer-implemented system of claim 49 wherein the OS agent determines metadata for the process and metadata for the operating system, detects a communication with another process running on a second operating system on a second host device; and sends a communication topology event over the network to the monitoring node, where the communication topology event includes information identifying the process group, information identifying the operating system, a network address and port identifier for host computing device and a network address and port identifier for the second host device.

### Claim 54 (depends on 53)

The computer-implemented system of claim 53 further comprises a topology processor residing on the monitoring mode and configured to receive the communication topology event from the host computing device and a second communication topology event from the second host device, where the second communication topology event includes information identifying a process group to which the another process belongs, information identifying the second operating system, the network address and port identifier for the host computing device and the network address and port identifier for the second host device, wherein the topology processor determines a horizontal relationship between the process group of the process and the second process group of the another process system using the communication topology event and the second communication topology event; and creates a record for the horizontal relationship in a topology repository.

### Claim 55 (depends on 53)

The computer-implemented system of claim 53 further comprises a virtualization agent, the virtualization agent detects host computing devices implemented as virtualized computer systems, generates a virtualization topology event for the detected virtualized computer system, and sends the virtualization topology event over a network to the monitoring node, where the virtualization topology event includes an identifier for the virtualized computer system and an identifier for a network interface assigned to the virtualized computer system.

### Claim 56 (depends on 55)

The computer-implemented system of claim 55 wherein the OS agent determines information identifying an operating system running on the host computing device, generates an OS topology event and sends the OS topology event over the network to the monitoring node, where the OS topology event includes data identifying the operating system and the identifier for a network interface assigned to the host computing device; and a topology processor receives the OS topology event and identifies a virtualized computer system for the host computing device using the identifier for the network interface, where the topology processor resides on the monitoring mode.
