eG Help

If traffic to a web application is found to be bandwidth-intensive, administrators may instantly want to know which specific URL in that application is actually hogging the bandwidth resources. Administrators may later want to block access to these URLs, so as to conserve bandwith. Likewise, if user experience with a web application deteriorates, administrators may want to swiftly check the responsiveness of each URL requested by the user, to identify which URL is adversely impacting the user experience and why. The CtxNsIsWebUrlTest test helps administrators with this.

This test automatically discovers the URLs accessed by users and reports the number of requests received and bandwidth used per URL. This way, the test pinpoints those URLs that are accessed frequently and the ones that generate bandwidth-intensive web traffic. Additionally, the test also reports the page load time and render time of every URL, so that, when a slowdown occurs, administrators can instantly identify the URL that resulted in a slow response and where the slowdown occurred – when the requested page was loaded? Or when it was rendered by the client?

Measurement	Description	Measurement Unit	Interpretation
Hits	Indicates the number of requests received for this URL.	Number	Compare the value of this measure across URLs to identify the URL that is most popular. Use the detailed diagnosis of this measure to know the IP address of the NetScaler ADC that received requests for this URL, the host name of the NetScaler, and the IP address of the web server that processed requests for this URL.
Bandwidth	Indicates the total amount of data received from this URL.	KB	Compare the value of this measure across URLs to know the web traffic to which URL has been consistently consuming more bandwidth than the rest.
Load_time	Indicates the elapsed time, from when the browser starts to receive the first byte of a response until the user starts to interact with the page. At this stage, some of the page content might not yet have been loaded.	msecs	A high value for this measure is a cause for concern as it indicates that the requested web page is taking too long to load. In the event of a slowdown, you may want to compare the value of this measure with that of the Render_time measure to accurately determine the reason for the slowness – is it because of a delay in page loading? Or page rendering?
Render_time	Indicates the elapsed time, from when the browser starts to receive the first byte of a response until either all page content has been rendered or the page load action has timed out.	msecs	A high value for this measure indicates that the client is having problems rendering the requested pages. In the event of a slowdown, you may want to compare the value of this measure with that of the Load_time measure to accurately determine the reason for the slowness – is it because of a delay in page loading? Or page rendering?
Cache_hits	Indicates the number of requests to this URL that was serviced by the cache.	Number	If the value of this measure is the same as that of the Hits measure, it implies that all requests to the URL were serviced by the cache server. This is indicative of optimal cache size and usage. On the other hand, if the value of this measure is much lower than that of the Hits measure, it could indicate improper cache sizing and ineffective cache usage. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_miss	Indicates the number of requests to this URL not serviced by the cache.	Number	Ideally, the value of this measure should be 0 or at least, very low. If the value is the same as that of the Hits measure, it could indicate improper cache sizing and ineffective cache usage. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_hit_ratio	Indicates the percentage of requests to this URL that were serviced by the cache.	Percent	Ideally, the value of this measure should be > 80%. A low hit ratio on the other hand indicates that a majority of web requests were serviced by the origin server and not the cache server. This can significantly increase request processing time and related overheads. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_bypass	Indicates the number of requests to the URL that were serviced by the origin server, because the cache server was bypassed.	Number	This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_hits_bw_consumed	Indicates the bandwidth consumed when requests to this URL were serviced by the cache server.	KB	The difference between the value of the Bandwidth measure and this measure for a URL will reveal the bandwidth that may have been saved by request caching. Where cache is well-sized and used optimally, this difference will be high. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_miss_bw_consumed	Indicates the bandwidth consumed when the cache server could not serve the requests to this URL.	KB	The difference between the value of this measure and the value of the Cache_hits_bw_consumed measure for a web server will reveal how much bandwidth was saved by cache hits. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.
Cache_bypass_bw_consumed	Indicates the bandwidth consumed when the cache server was bypassed and the requests to this URL were served from the origin server.	KB	If the difference between the value of this measure and that of the Cache_miss_bw_consumed measure results in a ‘positive’ integer, it indicates that cache usage has saved considerable bandwidth. This measure will not be reported for Citrix NetScaler Insight versions lesser than v11.x.