eG Help

One of the key value propositions of the NetScaler ADC is its ability to optimize user experience by making web applications run faster and by delivering them to users more quickly. If users continue to complain of slowness when accessing applications despite the usage of NetScaler ADC, it will beat the very purpose of the NetScaler ADC, forcing enterprises to hunt for alternative delivery controllers. To avoid such an eventuality, administrators should be able to detect a current/potential slowdown in a web application well before users notice, isolate the source of the slowness, and address it rapidly. This is where the CtxNsIsWebAppTest test helps!

This test monitors how responsive each web application delivered by NetScaler ADC is to user requests and promptly notifies administrators if any application’s responsiveness dips. Upon receiving such intimations, administrators can once again zoom into the test to figure out the reason for the slowness- is it because the web server hosting the application is unable to process requests quickly? is it owing to a latent server-side network? or is it due to a latent client-side network?

Measurement	Description	Measurement Unit	Interpretation
Hits	Indicates the number of requests received by this web application.	Number	This is a good indicator of the load on the web application. Compare the value of this measure across web applications to know which application is the most popular. Use the detailed diagnosis of this measure to know which web server is hosting the application and which NetScaler is managing it.
Bandwidth	Indicates the total amount of data received by this web application.	KB	Compare the value of this measure across web applications to know which web application is consuming bandwidth excessively.
Response_time	Indicates the elapsed time between the end of an enquiry and the beginning of a response from this application.	msecs	A high value for this measure indicates that the application is processing requests slowly. If this measure reports an abnormally high value for an application, compare the value of the Server_processing_time, Client_network_latency, and Server_network_latency measures of that application to determine the reason for the slowness.
Server_processing_time	Indicates the elapsed time, from when the server starts to receive the first byte of a request from the NetScaler appliance until the NetScaler appliance receives the first byte to response.	msecs	A high value for this measure indicates that the web server is processing requests slowly. If the Response_time measure reports an abnormally high value for a web application, then compare the value of this measure with that of the Client_network_latency and Server_network_latency measures of that application to determine what is causing the slowness – the poor processing power of the web server? a latent server network? or a slow client network?
Client_network_latency	Indicates the average latency caused by the client network.	msecs	A high value for this measure indicates that the client network is latent. If the Response_time measure reports an abnormally high value for a web application, then compare the value of this measure with that of the Server_network_latency and Server_processing_time measures of that application to determine what is causing the slowness – the poor processing power of the web server? a latent server network? or a slow client network?
Server_network_latency	Indicates the average latency caused by the server network.	Msecs	A high value for this measure indicates that the server network is latent. If the Response_time measure reports an abnormally high value for a web application, then compare the value of this measure with that of the Client_network_latency and Server_processing_time measures of that application to determine what is causing the slowness – the poor processing power of the web server? a latent server network? or a slow client network?