Debugging application performance over a network

• US 20060029016A1
• Filed: 06/22/2005
• Published: 02/09/2006
• Est. Priority Date: 06/29/2004
• Status: Abandoned Application

• Current Assignee: Radware Limited
• Original Assignee: Radware Limited
• Inventors: Peles, Amir
• Application Number:
  US11/158,888
• Publication Number:
  US 20060029016A1
• Time in Patent Office: Days
• US Class Current: 370/328
• CPC Class Codes: H04L 43/022 by sampling
• CPC Class Codes: H04L 43/106 using time related information in packets, e.g. by adding timestamps
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

An application debugging switch also monitors application performance. The application debugging switch forwards the requests from a first host to a second host, and later forwards the response coming from that second host to that first host. As most of the applications work in a request—response architecture, the application debugging switch can measure the response time of the application. The switch attaches a timestamp to each request that it forwards. When the response to that request comes to the switch, the switch can determine the response time of that application. The application debugging switch collects multiple samples of response time over a certain period of time. These samples provide a good measurement for the average application response time. The response time is a combination of the network response time and the application response time. The application debugging switch holds multiple measurement classes. Each class defines different sources or destinations of traffic (IP addresses and networks) and different applications (TCP/UDP ports or content identifiers in the requests). Collecting the response time for each class separately allows zooming in to an application and user that experience bad service and detect the reason for their failure.

Claims

1. A method to monitor response times associated with client(s) and server(s) located in a network, said method implemented in an application debugging switch among a plurality of said application debugging switches dispersed over said network, said method comprising the steps of:

receiving a request from a client intended for a server and identifying and storing a timestamp t1 when said request is received;

forwarding said request to said server;

receiving a response from said server and identifying and storing timestamp t2 when said response is received, and

calculating a server response time as a difference between t2 and t1,

wherein said calculated server response time identifies indicates network and application responsiveness.

2. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said method further comprises the steps of:

forwarding said response to said client and storing timestamp t3 when said response is forwarded;

receiving an acknowledgement from said client, storing timestamp t4 when said response is received, and

calculating a client response time as a difference between t4 and t3.

3. A method to monitor response time associated with client(s) and server(s) located in a network, as per claim 2, wherein said acknowledgement from said client is a request from said client.

4. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said network is any of the following:

local area network (LAN), wide area network (WAN), or the Internet.

5. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said request is an IP request.

6. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said request is based on any of the following protocols:

TCP/IP, HTTP, DNS, SSL, IMAP, POP3, SMTP, FTP, RTSP, SIP, H.323, NFS, NNTP, LDAP, or RADIUS.

7. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said server is part of a plurality of servers in a cluster and said application debugging switch uses load balancing decisions to select a server in said cluster for forwarding communication from said client.

8. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 7, wherein said load balancing decision is based on said server response time of each server in said cluster

9. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 7, wherein said load balancing decision is based on any of the following:

current user load of each server in said cluster, current traffic load of each server in said cluster, current availability and health of each server in said cluster, administrative operation status of each server in said cluster, a weight reflecting a resource capacity of each server in said cluster, responsiveness of each server in said cluster, packet loss of each server in said cluster, or error rate of transactions in each server in said cluster.

10. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said application debugging switch maintains a policy statistic table defining classes and comprising any of, or a combination of, the corresponding bandwidth and sampling rate of traffic to be monitored.

11. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said application debugging switch maintains a policy statistic table defining classes of traffic to be monitored.

12. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 11, wherein said policy statistic table further comprises any of, or a combination of, the following parameters:

number of new sessions initiated in a prior period, number of active ongoing sessions, amount of bandwidth consumed in a prior period or peak bandwidth value for a predefined prior period.

13. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said application debugging switch further comprises a policy threshold table maintaining one or more of the following thresholds:

amount of bandwidth, number of active sessions, number of new sessions per period or amount of packet loss, with said application debugging switch either terminates traffic or notifies an external entity when said thresholds are breached.

14. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 1, wherein said application debugging switch further comprises a policy threshold table maintaining a server response time threshold, with said application debugging switch either terminates traffic or notifies an external entity when said threshold is breached.

15. A method implemented in an application debugging switch to identify bottlenecks associated with a server based on monitoring network and application response times associated with a plurality of clients and said server, said method comprising the steps of:

receiving a plurality of requests from said plurality of clients to said server;

forwarding said plurality of requests to said server and monitoring network and application response times, said plurality of requests targeting a combination of any of the following;

a communication protocol stack supported by said server, application logic of said server, storage resources of said server, operating system resources of said server, or CPU resources of said server;

storing timestamps associated with said plurality of transmitted requests;

receiving a plurality of responses from said server, identifying and storing a timestamp for each received response;

calculating server response time for each received response as a difference between timestamp of each received response and a timestamp associated with a corresponding transmitted request; and

identifying network and application bottlenecks associated with said server based on said calculated server response times.

16. The method per claim 15, wherein said method further comprises the steps of:

forwarding each of said plurality of responses to a corresponding client and storing a timestamp when said response is forwarded;

receiving an acknowledgement from said client and storing a timestamp when said response is received;

calculating client response time for each forwarded response as a difference between the timestamp of each forwarded response and a timestamp associated with a corresponding acknowledgement, and

identifying network bottlenecks associated with said client based on said calculated client response times.

17. The method per claim 15, wherein said network is any of the following:

local area network (LAN), wide area network (WAN), or the Internet.

18. The method per claim 15, wherein said request is based on any of the following protocols:

TCP/IP, HTTP, DNS, SSL, IMAP, POP3, SMTP, FTP, RTSP, SIP, H.323, NFS, NNTP, LDAP, or RADIUS.

19. The method per claim 15, wherein said request targeting a communication protocol is an IP request.

20. A networking system comprising:

a plurality of application debugging switches dispersed throughout a network, each application debugging switch;

receiving a request from a client to a server;

forwarding said request to said server and storing timestamp t1 when said response is forwarded;

receiving a response from said server and storing timestamp t2 when said response is received, and

calculating a server response time as a difference between t2 and t1, and

a debugging center collecting response time information from said plurality of application debugging switches and mapping application and/or network responsiveness.

21. A networking system, as per claim 20, wherein said request targeting any of, or a combination of, any of the following:

a communication protocol stack supported by said server, application logic of said server, storage resources of said server, operating system resources of said server, or CPU resources of said server;

22. A networking system, as per claim 20, wherein said network is any of the following:

local area network (LAN), wide area network (WAN), or the Internet.

23. A networking system, as per claim 20, wherein said application debugging switch further forwarding said response to said client and storing timestamp t3 when said response is forwarded, receiving an acknowledgement from said client, storing timestamp t4 when said response is received by said client, and calculating a client response time as a difference between t4 and t3.

24. A networking system comprising:

at least one application debugging switch facilitating communication between one or more clients and at least one application server and collecting statistics comprising network response times and application response times associated with said server;

at least one policy logging server maintaining one or more policies defining mathematical operations on collected statistics, wherein said at least one application debugging switch performs mathematical operations on said collected statistics according to a predefined policy in said policy logging server; and

wherein said collected statistics are used to map application and network responsiveness.

25. A networking system, as per claim 24, further comprising:

at least one record logging server receiving collected statistics operated on according to a predefined policy in said at least one policy logging server.

26. A networking system, as per claim 24, wherein said network is any of the following:

local area network (LAN), wide area network (WAN), or the Internet.

27. A networking system, as per claim 24, wherein said at least one policy logging server maintains a policy logging report comprising any of the following entries:

policy index, average response time/peak response time, average/peak failed transaction ratio, or average/peak packet loss ratio.

28. A networking system, as per claim 25, wherein said at least one record logging server comprises a record logging report comprising any of the following entries:

source IP address, destination IP address, application type, content type, session start, session end, size of content, response time, losses, or reason of failure.

29. A method to monitor response times associated with client(s) and server(s) located in a network, said method implemented in at least two application debugging switches dispersed over said network, said method comprising the steps of:

receiving, at a first debugging switch, a request from a client intended for a server, said first application debugging switch;

identifying a timestamp t11 when it receives said request;

forwarding said request to said server;

receiving said forwarded request at a second debugging switch, said second debugging switch;

identifying a timestamp t21 when it receives said forwarded request;

forwarding said request to said server;

receiving a response from said server;

identifying a time stamp t22 when said response is received in said server, and forwarding said response to said client;

receiving said forwarded response at said first application debugging switch, said first application debugging switch;

identifying a timestamp t12 when said forwarded response is received;

forwarding said response to said client,

wherein a first response time RT1 is calculated in said first application debugging switch as the difference between response times t12 and t11 and a second response time RT2 is calculated at said second debugging switch as difference between response times t22 and t21, said response times identifying network and application responsiveness.

30. A method to monitor response times associated with client(s) and server(s) located in a network, as per claim 29, wherein said response times RT1 and RT2 are forwarded to a debugging center, said debugging center calculating a response time RT as the difference between RT1 and RT2, said difference RT identifying network bottlenecks between said first and second application debugging switch.

31. A networking system comprising:

a traffic generation machine generating network traffic;

a plurality of application debugging switches, wherein at least one application debugging switch;

receives a plurality of requests generated by said traffic generation machine intended for a server on said network, identifies and stores timestamps when said requests are received,

forwards said plurality of requests to said server;

receives a plurality of responses corresponding to said plurality of requests from said server,

identifies and stores timestamps when said responses are received and calculates response times as a difference between the time stamp when a request is received and the time stamp when a response is sent,

wherein said at least one application debugging switch in conjunction with the traffic generation machine increases the generated traffic intended for said server, calculates response time for said generated traffic, and identifies the amount of traffic when a failure threshold is reached.

32. A method implemented in an application debugging switch to monitor response times in phases for application transactions between a client to a plurality of servers, plurality of said application debugging switches dispersed over a network, said method comprising the steps of:

receiving a TCP connection request from said client and forwarding said TCP connection request to an application server at timestamp t1;

receiving a TCP acknowledgement message from said application server at timestamp t2, calculating a TCP response time as t2-t1, and forwarding said TCP acknowledgement message to said client;

receiving an application request from said client and forwarding said application request to said application server at timestamp t3;

receiving an application reply from said application server at timestamp t4, calculating an application response time as t4-t3, and forwarding said application reply to said client, and

wherein said application debugging switch measures response time of each phase in a transaction to identify responsiveness of each phase of said transaction.

33. The method per claim 32, said method further comprising the steps of:

receiving a DNS query from a DNS client and forwarding said DNS query to a DNS server at timestamp t5;

receiving a DNS response from said DNS server at timestamp t6, calculating a DNS server response time as t6-t5, and forwarding said DNS response to said DNS client.