Synthetic transaction monitor with replay capability
First Claim
1. A method for monitoring synthetic transactions comprising:
- pre-scanning a set of recorded client-server transactions to identify and set up server-side connections including approximating objects associated with the client-server transactions and which changed after the set of client-server transactions was recorded, wherein the set of recorded client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call;
playing back the set of recorded client-sewer transactions on a client;
monitoring selected parameters associated with the set of recorded client-server transactions;
identifying differences between actual and recorded Hypertext Markup Language (HTML) object trees and modifying recorded requests prior to issuance of the requests in playback, wherein modifying recorded requests comprises identifying objects in the actual HTML object tree to replace objects in the recorded requests, wherein the replaced objects do not exist in identical form in the actual HTML object tree; and
transmitting performance data associated with the selected parameters to a server.
11 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods for recording and replaying client-server transactions on selected clients in order to gauge the performance of the client-server system from the perspective of the client. In one embodiment, a method comprises playing back a set of recorded transactions on a client, monitoring selected performance-related parameters at the client, and transmitting monitored data to the server for analysis or for viewing by a system administrator. The set of transactions is recorded on a first client by replacing a standard Internet transaction driver (e.g., WinInet.DLL) with a modified driver that is configured to intercept function calls. The function calls and corresponding parameters are recorded in a file which is later transmitted to a client, where the recorded transaction information is used to reproduce the transactions on the client. As the transactions are played back, performance data may be monitored and forwarded to a management server for analysis, display, etc.
-
Citations
20 Claims
-
1. A method for monitoring synthetic transactions comprising:
-
pre-scanning a set of recorded client-server transactions to identify and set up server-side connections including approximating objects associated with the client-server transactions and which changed after the set of client-server transactions was recorded, wherein the set of recorded client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call; playing back the set of recorded client-sewer transactions on a client; monitoring selected parameters associated with the set of recorded client-server transactions;
identifying differences between actual and recorded Hypertext Markup Language (HTML) object trees and modifying recorded requests prior to issuance of the requests in playback, wherein modifying recorded requests comprises identifying objects in the actual HTML object tree to replace objects in the recorded requests, wherein the replaced objects do not exist in identical form in the actual HTML object tree; andtransmitting performance data associated with the selected parameters to a server. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A computer-readable storage medium containing one or more instructions, stored thereon, which when executed by a processor cause a computer to perform a method comprising:
-
pre-scanning a set of recorded client-server transactions to identify and set up server-side connections including approximating objects associated with the client-server transactions and which changed after the set of client-server transactions was recorded, wherein the set of client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call and wherein the set of recorded client-server transactions was recorded on a first client; playing back the set of recorded client-server transactions on a second client; monitoring selected requests associated with the playing back of the set of recorded client-server transactions;
identifying differences between actual and recorded Hypertext Markup Language (HTML) object trees and modifying recorded requests prior to issuance of the requests in playback, wherein modifying recorded requests comprises identifying objects in the actual HTML object tree to replace objects in the recorded requests, wherein the replaced objects do not exist in identical form in the actual HTML object tree; andtransmitting data associated with the selected requests to a server. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification