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 and logs statistics
regarding the maximum number of transactions occurring per second (TPS)
and the amount of traffic moving through the system.
Note: Maximum request and response throughput is collected and recorded separately. Each value is then displayed separately when you drill down into details of Transaction Outcomes ( ).
|HTTP Timing (RTT, TTFB, Duration)||Collects and logs statistics regarding the HTTP request and response times, including round-trip time, time to first byte and overall transaction duration time.|
|Page Load Time||Collects and logs statistics
regarding the time 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 geographic location and connection types.
|User Sessions||Collects and logs statistics
regarding the number of unique user sessions. For Timeout, select the
allowed minutes of user inactivity before the system considers the
session to be over.
For Cookie Secure Attribute, specify whether to secure session cookies:
|URLs||Saves the URLs that were requested.|
|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 HTTP Analytics profile.|
|Response Codes||Saves HTTP response codes that the server returned in response to requests.|
|User Agents||Saves information about browsers making the request.|
|Methods||Saves HTTP methods in requests.|
|OS and Browsers||Saves information about the operating system and browser making the request.|
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.