Synthetic transaction monitor with replay capability

• US 7,966,398 B2
• Filed: 03/17/2009
• Issued: 06/21/2011
• Est. Priority Date: 03/30/2001
• Status: Expired due to Fees

• Current Assignee: BMC Software Incorporated (KKR & Co., Inc.)
• Original Assignee: BMC Software Incorporated (KKR & Co., Inc.)
• Inventors: Wiles, Philip V. Jr.
• Primary Examiner(s): Dalencourt; Yves
• Application Number:
  US12/405,939
• Publication Number:
  US 20090240765A1
• Time in Patent Office: 826 Days
• Field of Search: 709/203, 709/205, 709/219, 709/224, 709/225
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/87 Monitoring of transactions
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5012 determining service availability, e.g. which services are available at a certain point in time
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: Y10S 707/99931 Database or file accessing

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.

Claims

1. A system for monitoring synthetic transactions comprising:

a server computer;

a set of client computers coupled to the server computer on a network, wherein client-server transactions are conducted between each of the set of client computers and the server computer and wherein each client computer comprises a non-transitory computer readable medium having instructions embodied thereon, the instructions executable for playing back a set of recorded client-server transactions occurring between the server computer and at least one of the set of client computers;

a monitor computer coupled to the server computer and the set of client computers on the network, comprising a non-transitory computer readable medium having instructions embodied thereon, the instruction executable for;

pre-scanning the set of recorded client-server transactions occurring between the server computer and at least one of the set of client computers to identify server-side connections including a recorded object associated with the client-server transactions, wherein the object changed after the set of client-server transactions was recorded and the set of recorded client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call or at least one Internet API call;

monitoring selected parameters associated with the set of recorded client-server transactions;

playing back the set of recorded client-server transactions, wherein playing back the set of recorded client-server transactions comprises determining an actual object corresponding to the recorded object and identifying if there is a difference between the recorded object and the actual object; and

transmitting performance data associated with the selected parameters to the server.

2. The system of claim 1, wherein the set of recorded client-server transactions comprises a TCP/IP transaction, a File Transfer Protocol (FTP) transaction or a web browser transaction.

3. The system of claim 1, wherein a match percentage is computed by comparing HTML source associated with the recorded object to HTML source received during playback.

4. The system of claim 1, further comprising selecting a nearest approximation to the recorded object.

5. The system of claim 1, wherein the nearest approximation is based on a server name and a path associated with the recorded object.

6. The system of claim 1, wherein the monitor computer is one of the set of client computers.

7. The system of claim 1, wherein the playing back of the recorded client-server transactions comprises modifying a recorded requests prior to issuance of the requests, by identifying the actual object in an actual HTML object tree to replace the recorded object if the recorded object does not exist in identical form in the actual HTML object tree.

8. The system of claim 1, wherein the monitor computer is one of the set of client computers or the server computer.

9. A non-transitory computer-readable storage medium containing one or more instructions, wherein the one or more instructions are when executed by a processor cause a computer to perform a method comprising:

pre-scanning a set of recorded client-server transactions occurring between a server computer and at least one of a set of client computers to identify server-side connections including a recorded object associated with the client-server transactions, wherein the object changed after the set of client-server transactions was recorded and the set of recorded client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call or at least one Internet API call;

monitoring selected parameters associated with the set of recorded client-server transactions;

playing back the set of recorded client-server transactions, wherein playing back the set of recorded client-server transactions comprises determining an actual object corresponding to the recorded object and identifying if there is a difference between the recorded object and the actual object; and

transmitting performance data associated with the selected parameters.

10. The computer readable medium of claim 9, wherein the set of recorded client-server transactions comprises a TCP/IP transaction, a File Transfer Protocol (FTP) transaction or a web browser transaction.

11. The computer readable medium of claim 9, wherein a match percentage is computed by comparing HTML source associated with the recorded object to HTML source received during playback.

12. The computer readable medium of claim 9, wherein the method further comprises selecting a nearest approximation to the recorded object.

13. The computer readable medium of claim 9, wherein the nearest approximation is based on a server name and a path associated with the recorded object.

14. The computer readable medium of claim 9, wherein the playing back of the recorded client-server transactions comprises modifying a recorded requests prior to issuance of the requests, by identifying the actual object in an actual HTML object tree to replace the recorded object if the recorded object does not exist in identical form in the actual HTML object tree.

15. A method comprising:

pre-scanning a set of recorded client-server transactions occurring between a server computer and at least one of a set of client computers to identify server-side connections including a recorded object associated with the client-server transactions, wherein the object changed after the set of client-server transactions was recorded and the set of recorded client-server transactions includes at least one Transmission Control Protocol/Internet Protocol (TCP/IP) function call or at least one Internet API call;

monitoring selected parameters associated with the set of recorded client-server transactions;

playing back the set of recorded client-server transactions, wherein playing back the set of recorded client-server transactions comprises determining an actual object corresponding to the recorded object and identifying if there is a difference between the recorded object and the actual object; and

transmitting performance data associated with the selected parameters.

16. The method of claim 15, wherein the set of recorded client-server transactions comprises a TCP/IP transaction, a File Transfer Protocol (FTP) transaction or a web browser transaction.

17. The method of claim 15, wherein a match percentage is computed by comparing HTML source associated with the recorded object to HTML source received during playback.

18. The method of claim 15, further comprising selecting a nearest approximation to the recorded object.

19. The method of claim 15, wherein the nearest approximation is based on a server name and a path associated with the recorded object.

20. The method of claim 15, wherein the playing back of the recorded client-server transactions comprises modifying a recorded requests prior to issuance of the requests, by identifying the actual object in an actual HTML object tree to replace the recorded object if the recorded object does not exist in identical form in the actual HTML object tree.