Monitoring Radware AppDirector

eG Enterprise offers a special-purpose monitoring model for the Radware AppDirector to monitor the status and overall performance of the target Radware AppDirector.

Figure 1 depicts the layer model of a Radware AppDirector.

Figure 1 : Layer model for Radware AppDirector

Every layer in the Figure 1 is mapped to various tests to determine the critical statistics related to the performance of the target Radware AppDirector. Using the metrics reported by the tests, administrators can find accurate answers for the following performance queries:

  • How well data/packets are transmitted/received over each AD Farm? Is there any AD Farms that transmit/recieve maximum packets/data?

  • How well DNS and Triangularization requests were received, answered and re-directed by each AD farm? Is there any AD Farm with high load?

  • How well HTTP sessions were received and re-directed by each AD farm? Is there any AD Farm with high load?

  • How well RTSP, SIP, and Proxy requests were received and re-directed by each AD farm? Is there any AD Farm with high load?

  • Is the number of TCP connections disconnected from the AD server(AppDirector Farm) is high?

  • How well data/packets are transmitted/received over each AD server(AppDirector Farm)? Is there any AD server(AppDirector Farm) that transmit/recieve maximum packets/data?

  • How well DNS and Triangularization requests were receivedand answered by each AD server(AppDirector Farm)? Is there any AD server(AppDirector Farm) with high load?

  • How well HTTP, RTSP, SIP, and Proxy session requests were re-directed by each AD server(AppDirector Farm)? Is there any AD server(AppDirector Farm) with high load?

  • Is the CPU and Network utilization of the target Radware Appdirector abnormally high?

  • How well DNS and Triangularization requests were receivedand answered by the application servers? Is there any application server with high load?

  • How well HTTP, RTSP, SIP, and Proxy session requests were re-directed by each application server? Is there any application server with high load?

  • Is any application servers Not in Service or disabled?

  • Is the number of users accesing the server very high? if so, how many?

  • Is any application servers consuming bandwidth excessively?

  • How well DNS and Triangularization requests were received, answered and re-directed by each Web farm? Is there any Web farm with high load?

  • How well HTTP sessions were received and re-directed by each Web farm? Is there any Web farm with high load?

  • How well RTSP, SIP, and Proxy requests were received and re-directed by each Web farm? Is there any Web farm with high load?

  • Is any WSD farm servers Not in Service or disabled?

  • Is the number of connection rquests denied by the WSD farm is too high?if so, how many?

  • Is any WSD farms consuming bandwidth excessively?

    Since the tests mapped to the Network Layer have been elaborately discussed in Monitoring Cisco Router document, the sections to come will discuss the other layers in detail.