The Behavior Tracking Servlet Filter

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.7. Defining BehaviorTrackingFilter in web.xml

<?xml version="1.0"?>
<web-app xmlns=""
   <!-- normal web.xml configuration up to this point -->
   <!-- enable behavior tracking for servlet requests -->



An optional comma-separated list of parameters to include in the event data logs. If unspecified, all parameters are logged.


An optional comma-separated list of parameters to include with the request URI in the event name. If unspecified, no parameters are included in the name.


The value to specify for "event-type" in the event data logs. Primarily useful if you want to define several different filters and be able to identify which generated each event. Defaults to "http-request" if unspecified.


The Spring bean name of the BehaviorTrackingManager used to log events. Defaults to "defaultTrackingManager" if unspecified (if you only have one <bt:manager> tag in your Spring configuration, you should not need this parameter).