As mentioned in Chapter 1, Quick Start, HTTP request tracking can be enabled either in spring configuration via inclusion of <bt:http-requests> or as a servlet filter. The primary difference is that the serlvet filter can record response codes and error messages in the event log.
Example 3.6. Defining BehaviorTrackingFilter in web.xml
<?xml version="1.0"?> <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4"> ... <!-- normal web.xml configuration up to this point --> <!-- enable behavior tracking for servlet requests --> <filter> <filter-name>trackingFilter</filter-name> <filter-class>com.mtgi.analytics.servlet.BehaviorTrackingFilter</filter-class> <init-param> <param-name>com.mtgi.analytics.parameters.include</param-name><param-value>dispatch</param-value> </init-param> <init-param> <param-name>com.mtgi.analytics.servlet.event</param-name>
<param-value>http-request</param-value> </init-param> <init-param> <param-name>com.mtgi.analytics.manager</param-name>
<param-value>defaultTrackingManager</param-value> </init-param> </filter> <filter-mapping> <filter-name>trackingFilter</filter-name> <servlet-name>action</servlet-name> <dispatcher>REQUEST</dispatcher> </filter-mapping> </web-app>