In continuation to the announcement of NetScaler Insight 1.0 Beta release (http://blogs.citrix.com/2012/08/31/netscaler-insight-redefines-application-visibility/), in this blog we will explore how NetScaler Insight 1.0 can help you understand your application performance to the depth!
Information has a multifaceted purpose across all domains. It can do wonders if received at the right time in the right format. When something like this put together across a component high in demand, it becomes a gold mine.
NetScaler Insight puts together this lethal combination of the precise Application Performance information in the desired right format!
NetScaler Insight 1.0 brings you all that you want to know about your applications under one roof and answers multiple questions like mentioned below. With these questions we will unveil several layers of information’s that NetScaler Insight brings to the table.
- Layer 1 – Which are the NetScaler ADC appliances managing most of my applications traffic?
- It gives you a clear idea with respect to Hits and Bandwidth consumption across all of your NetScaler ADC appliances on how your applications are being managed by the NetScaler ADCs deployed in your infrastructure.
- Layer 2 – How many applications are being managed by one of my NetScaler ADC in the deployment?
- It can take you from the NetScaler ADC appliance consuming most of the bandwidth to the details of which applications it is managing to get the highest BW consumption across your deployment.
- Layer 3 – Which one of these applications has highest response time?
Beyond the bandwidth consumption details, you can always select Response time and understand the response time distribution of applications. This way you can also drill down from high response time and go deeper to identify the pain point.
- Layer 4 – Can I understand the reason behind such high response time?
The next level of information you get is the distribution of that one aggregated response time number into a time line chart. That one response time is plotted across client network latency, server network latency and server processing time. With this distribution, you can clearly pin point which component of the response time is contributing to the overall high response time.
With four layers unwrapped, we will keep the rest of the layers under the hood and reveal them in the next series of blogs. Till then sit tight and look forward to a lot more that’ll be showcased in the upcoming blogs!