# US 2017/0250890 A1 · Asynchronous transactions reported as critical path

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

- Number: US 2017/0250890 A1
- Document ID: US20170250890A1
- Status: Published application
- Kind: A1
- Application number: 15/057,020
- Filed: 2016-02-29
- Published: 2017-08-31
- Earliest claimed: 2016-02-29
- Assignees: New Relic, Inc.
- Applicants: New Relic, Inc.
- Inventors: Ashley Emmons Puls; Michael Hayes; Howard G. Cunningham, JR.; Kirby Frugia; Gregory Eugene Unrein; Etan Lightstone
- Web page: https://patentgrep.com/patent/US20170250890A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 9/466: {Transaction processing}
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An agent executed by a computer identifies a critical path of a transaction in a web application. The transaction includes a plurality of methods each representing an operation of the application and asynchronously executed by a server between a beginning of the transaction and an end of the transaction. The agent receives metrics for the transaction, which include identifiers of each executed method and specify relationships between the transaction methods. Based on the received metrics, the agent identifies a method completed at the end of the transaction. Based on the relationships between the methods, the agent determines one or more other methods preceding the identified method in the transaction and affecting a duration of the transaction. The determined methods and the method completed at the end of the transaction are identified as a critical path. Identifiers of the methods on the critical path are sent for display to a user.

## Claims

### Claim 1

A method for identifying a critical path of a transaction in a web application, the method comprising:
receiving, by a computer, metrics for a transaction in a web application, the transaction including a plurality of transaction methods, each method representing an operation of the web application asynchronously executed by a server between a beginning of the transaction and an end of the transaction, the metrics including identifiers of each executed transaction method and specifying relationships between the transaction methods;
identifying, by the computer and based on the received metrics, a transaction method of the plurality of transaction methods that is completed at the end of the transaction;
determining based on the relationships between the transaction methods, one or more other transaction methods preceding the identified method in the transaction and affecting a duration of the transaction;
identifying the determined transaction methods and the transaction method completed at the end of the transaction as a critical path of the transaction; and
sending identifiers of the transaction methods on the critical path for display to a user.

### Claim 2 (depends on 1)

The method of claim 1, wherein the transaction comprises a plurality of threads of execution each including one or more of the plurality of transaction methods.

### Claim 3 (depends on 2)

The method of claim 2, wherein determining the one or more other transaction methods comprises, for a transaction method on the critical path:
identifying based on the metrics, a beginning of the transaction method or a relationship to the transaction method by an earlier method in the transaction;
responsive to identifying the beginning of the transaction method, determining a next transaction method on the thread of execution including the transaction method as a next transaction method on the critical path;
responsive to identifying the relationship between the transaction method and the earlier transaction method, determining the earlier transaction method is a next transaction method on the critical path.

### Claim 4 (depends on 3)

The method of claim 3, wherein the relationship between the transaction method and the earlier transaction method comprises the earlier transaction method blocking the thread of execution including the transaction method.

### Claim 5 (depends on 1)

The method of claim 1, wherein the beginning of the transaction corresponds to a time the server received a request associated with the web application, and wherein the end of the transaction corresponds to a time the server transmitted a response to the request.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
injecting monitoring code into the web application, the monitoring code when executed generating the metrics.

### Claim 7 (depends on 1)

The method of claim 1, wherein the metrics further include start times of each transaction method, and wherein the method further comprises:
determining an execution time of each transaction method on the critical path based on the start times.

### Claim 8 (depends on 7)

The method of claim 7, wherein sending the identifiers on the transaction methods of the critical path for display to a user comprises:
generating a report for display to the user including the identifiers of the transaction methods on the critical path and the execution times of the transaction methods on the critical path.

### Claim 9 (depends on 7)

The method of claim 7, further comprising:
calculating a mean execution time of each transaction method on the critical path over a plurality of iterations of the transaction; and
generating a report for display to the user including the identifiers of the transaction methods on the critical path and the mean execution times.

### Claim 10

A non-transitory computer readable storage medium storing executable computer program instructions, the instructions when executed by a processor causing the processor to:
receive metrics for a transaction in a web application, the transaction comprising a plurality of transaction methods each representing an operation of the web application and asynchronously executed by a server between a beginning of the transaction and an end of the transaction, the metrics including identifiers of each executed transaction method and specifying relationships between the transaction methods;
identify, based on the received metrics, a transaction method of the plurality of transaction methods that is completed at the end of the transaction;
determine based on the relationships between the transaction methods, one or more other transaction methods preceding the identified method in the transaction and affecting a duration of the transaction;
identify the determined transaction methods and the transaction method completed at the end of the transaction as a critical path of the transaction; and
send identifiers of the transaction methods on the critical path for display to a user.

### Claim 11 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the transaction comprises a plurality of threads of execution each including one or more of the plurality of transaction methods.

### Claim 12 (depends on 11)

The non-transitory computer readable storage medium of claim 11, wherein determining the one or more other transaction methods comprises, for a transaction method on the critical path:
identifying based on the metrics, a beginning of the transaction method or a relationship to the transaction method by an earlier method in the transaction;
responsive to identifying the beginning of the transaction method, determining a next transaction method on the thread of execution including the transaction method as a next transaction method on the critical path;
responsive to identifying the relationship between the transaction method and the earlier transaction method, determining the earlier transaction method is a next transaction method on the critical path.

### Claim 13 (depends on 12)

The non-transitory computer readable storage medium of claim 12, wherein the relationship between the transaction method and the earlier transaction method comprises the earlier transaction method blocking the thread of execution including the transaction method.

### Claim 14 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the beginning of the transaction corresponds to a time the server received a request associated with the web application, and wherein the end of the transaction corresponds to a time the server transmitted a response to the request.

### Claim 15 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the instructions are further executable to cause the processor to:
inject monitoring code into the web application, the monitoring code when executed generating the metrics.

### Claim 16 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the metrics further include start times of each transaction method, and wherein the instructions are further executable to cause the processor to:
determining an execution time of each transaction method on the critical path based on the start times.

### Claim 17 (depends on 16)

The non-transitory computer readable storage medium of claim 16, wherein sending the identifiers on the transaction methods of the critical path for display to a user comprises:
generating a report for display to the user including the identifiers of the transaction methods on the critical path and the execution times of the transaction methods on the critical path.

### Claim 18 (depends on 16)

The non-transitory computer readable storage medium of claim 16, further comprising:
calculating a mean execution time of each transaction method on the critical path over a plurality of iterations of the transaction; and
generating a report for display to the user including the identifiers of the transaction methods on the critical path and the mean execution times.
