When you attach an Analytics (AVR) profile to a virtual server, the BIG-IP® system can gather, log, notify, and display statistical information about the traffic. You can associate a local traffic policy with a virtual server to further define which transactions to include or exclude in the statistics. Rules in the local traffic policy can enable or disable AVR for whatever type of traffic you want to define. You might want to do this to save system resources by not deploying Analytics on parts of the traffic that you are not interested in monitoring.
This implementation shows how to create an HTTP Analytics profile to store statistics locally. It then describes how to create a local traffic policy and add rules to the policy so that the Analytics module saves statistics for all traffic except that which has a URI containing the word index. (In this case, you are not interested in monitoring traffic directed towards index pages.)
Other options are available for configuring local traffic policies with Analytics. By following through the steps in this example, you can see the other options that are available on the screens, and can adjust the example for your needs.
|Max TPS and Throughput||Collects statistics showing the maximum number of transactions occurring per second and the amount of traffic moving through the system (maximum request and response throughput is collected and recorded separately). In the Details table of the Analytics: HTTP Transactions screen, if you drill down into a specific entity, the system displays the maximum TPS. Drilling down in the Request Throughput details displays the maximum request throughput for each entity; and drilling down in the Response Throughput details displays the maximum response throughput for each entity.|
|Page Load Time||Tracks how long it takes an application user to get a complete
response from the application, including network latency and completed
Note: End-user response times and latencies can vary significantly based on geography and connection types.
|User Sessions||Stores the number of unique user sessions. For
Timeout, select the number of minutes of user
inactivity to allow before the system considers the session to be over.
For Cookie Secure Attribute, specify whether to secure session cookies. Options are Always, the secure attribute is always added to the session cookie; Never, the secure attribute is never added to the session cookie; or Only SSL, the secure attribute is added to the session cookie only when the virtual server has a client SSL profile (the default value).
|URLs||Collects the requested URLs.|
|Countries||Saves the name of the country where the request came from, and is based on the client IP address criteria.|
|Client IP Addresses||Saves the IP address where the request originated. The address saved also depends on whether the request has an XFF (X-forwarded-for) header and whether the HTTP profile accepts XFF headers.|
|Client Subnets||Saves statistics for predefined client subnets. Client subnets can be added in the Subnets area of the default Analytics profile.|
|Response Codes||Saves HTTP response codes that the server returned to requesters.|
|User Agents||Saves information about browsers used when making the request.|
|Methods||Saves HTTP methods in requests.|
When you have completed the steps in this implementation, you have configured the BIG-IP® system to store statistics locally. A local traffic policy instructs the Analytics module to save statistics for all traffic except that which has a URI containing the word index.