Analytics DNS

Analytics DNS -

Analytics is the new talk in town. An analysis module connected to your network not only allow visibility in a supposedly "black box", but also help you to generate significant matrices of run time to make informed decisions and faster action. No wonder these modules are more "need" to "demand" customers. A multipurpose box as help 'NetScaler' you meet both your requirements and balancing analyzes need functional load.

NetScaler can function as a proxy server to a group of DNS servers. This allows you to draw performance and security benefits of NetScaler. As NetScaler can easily monitor traffic flow in and out, it gives you a nice GUI-based dashboard for various statistics related to your DNS server. But how to get top 'N' asked domains? hmm ... Tricky native analytics Action module NetScaler is your answer.

For those who are not familiar with the action of analysis can refer http://support.citrix.com/proddocs/topic/ns-main- AppExpert-10-1-card / ns -stream-analytics-wrapper-con.html to understand its basis. Here are the steps to follow to get the data on your 'NetScaler

1. Create a selection expression using CLIENT.UDP.DNS.DOMAIN
2. The use of this switch to create a stream identifier with the desired number of samples and the interval
3. Create a dns strategy, we will use "collect flow identifier for statistics created in step 2" as a rule for this policy and the link global with action as "no operation". Confused? Let me clarify

1. You need a policy to collect statistics for stream identifier as we refer here to a UDP server only option is to use a policy of DNS. These collection methods still work "true" if it is used in general
2. DNS policies are allowed to be bound only globally
3. as objective of this policy is to collect statistics, we will use a "DNS_NOP 'measures to ensure that no side effects add dns policy " ANALYTICS .STREAM ( " "). COLLECT_STATS "DNS-NOP
   bind dns World 100 65535 -gotoPriorityExpression kind REQ_DEFAULT

Go to action Analytics -> stream identifier; select stream identifier, click the action and select session flow. You will get a customizable dashboard here obtain the required statistics. here is an example for your reference

I am sure it is a great tool for reporting and monitoring for network administrators. Can we use these capabilities to gain functional benefits such as enabling better logging 'top limiting rate used urls' for some type queries? I'll leave that as an open question in the discussion. Do not comment if you have such a requirement and want us to help you achieve it.

How about requests grouping depending on the type of application or types of records (where you have more than one selector switch unlike one used in this example) and the collection of statistics for them. Stay tuned for the next blog to yet another feature of "NetScaler is amazing on this series

Tweet