IP Library Patent Application 14266654
Patent Application
App. No. 14/266,654

TRACING BUSINESS TRANSACTIONS BASED ON APPLICATION FRAMEWORKS

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
14/266,654
Abstract

A distributed transaction is traced to determine how it is handled by applications which process the distributed transaction at least in part without threads. To trace the transaction, the business transaction may be named based on the application framework that handles the transaction. The tracing occurs in application frameworks which do not include multiple threads for handling transactions, such as for example a PHP application framework. The present technology may detect the framework and framework calls, and then generate a name for a business transaction based on the detected information. The business transaction may then be named based on the loaded application framework.

Claims (59)

1 . A method for tracing a distributed transaction, comprising:

detecting a PHP application framework call to a remote server, the call part of a distributed transaction that occurs over multiple servers including at least one PHP application;

setting a business transaction name associated with the call;

modifying PHP framework call with the business transaction name; and

transmitting the modified PHP framework call to the remote server.

2 . The method of claim 1 , further comprising:

detecting framework loading;

setting a business transaction name based on the loaded framework; and

setting a business transaction type based on the loaded framework.

3 . The method of claim 1 , wherein the PHP framework call is detected before a framework is loaded, the method further comprising:

setting business transaction name based on an network address associated with the call; and

setting a business transaction type to a default value.

4 . The method of claim 1 , further comprising modifying the PHP framework call to include a unique request identifier.

5 . The method of claim 1 , further comprising:

retrieving call data by an agent; and

transmitting the call data by the agent.

6 . The method of claim 1 , further comprising transmitting a business transaction type, the business transaction name, and a call chain including a sequence of calls for the business transaction to a controller.

7 . The method of claim 6 , wherein the remote server receives the modified PHP framework call and reports processing of the call to the controller.

8 . The method of claim 7 , wherein the remote server includes a JAVA application which

9 . The method of claim 7 , wherein the remote server includes a .NET application.

10 . A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform a method for tracing a distributed transaction, the method comprising, comprising:

detecting a PHP application framework call to a remote server, the call part of a distributed transaction that occurs over multiple servers including at least one PHP application;

setting a business transaction name associated with the call;

modifying PHP framework call with the business transaction name; and

transmitting the modified PHP framework call to the remote server.

11 . The non-transitory computer readable medium of claim 10 , further comprising:

detecting framework loading;

setting a business transaction name based on the loaded framework; and

setting a business transaction type based on the loaded framework.

12 . The non-transitory computer readable medium of claim 10 , wherein the PHP framework call is detected before a framework is loaded, the method further comprising:

setting business transaction name based on an network address associated with the call; and

setting a business transaction type to a default value.

13 . The non-transitory computer readable medium of claim 10 , further comprising modifying the PHP framework call to include a unique request identifier.

14 . The non-transitory computer readable medium of claim 10 , further comprising:

retrieving call data by an agent; and

transmitting the call data by the agent.

15 . The non-transitory computer readable medium of claim 10 , further comprising transmitting a business transaction type, the business transaction name, and a call chain including a sequence of calls for the business transaction to a controller.

16 . The non-transitory computer readable medium of claim 15 , wherein the remote server receives the modified PHP framework call and reports processing of the call to the controller.

17 . The non-transitory computer readable medium of claim 16 , wherein the remote server includes a JAVA application which

18 . The non-transitory computer readable medium of claim 16 , wherein the remote server includes a .NET application.

19 . A system for tracing a distributed transaction, comprising:

a processor;

memory;

one or more modules stored in the memory and executable by the processor to detect a PHP application framework call to a remote server, the call part of a distributed transaction that occurs over multiple servers including at least one PHP application, set a business transaction name associated with the call, modify PHP framework call with the business transaction name, and transmit the modified PHP framework call to the remote server.

20 . The system of claim 19 , the one or more modules further executable to:

detect framework loading;

set a business transaction name based on the loaded framework; and

set a business transaction type based on the loaded framework.

21 . The system of claim 19 , wherein the PHP framework call is detected before a framework is loaded, the one or more modules further executable to:

setting business transaction name based on an network address associated with the call; and

setting a business transaction type to a default value.

22 . The system of claim 19 , the one or more modules further executable to modify the PHP framework call to include a unique request identifier.

23 . The system of claim 19 , the one or more modules further executable to:

retrieving call data by an agent; and

transmitting the call data by the agent.

24 . The system of claim 19 , the one or more modules further executable to transmit a business transaction type, the business transaction name, and a call chain including a sequence of calls for the business transaction to a controller.

25 . The system of claim 24 , wherein the remote server receives the modified PHP framework call and reports processing of the call to the controller.

26 . The system of claim 25 , wherein the remote server includes a JAVA application which

27 . The system of claim 25 , wherein the remote server includes a .NET application.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2017
From: APPDYNAMICS LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 044173/0050 →
CHANGE OF NAME Recorded Jun 23, 2017
From: APPDYNAMICS, INC.
To: APPDYNAMICS LLC
Reel/Frame 042964/0229 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 16, 2014
From: ZMIEVSKI, ANDREI; TUMMALA, RAMA KRISHNA
To: APPDYNAMICS, INC.
Reel/Frame 032917/0036 →