Filters

Filters are important for producing only the output necessary for a given monitoring task. A named URI, EJB, or client IP address can be specified and only the needed metrics data is produced. The performance load added to the containers by the Request Metrics component is reduced by adding more restrictive filters.

For HTTP requests arriving at a Web container, it is possible to filter on the URI and client IP address. For incoming requests to the EJB container, it is possible to filter on the bean method name and the client IP address. All the filters are listed and described here: Client IP address filters: Requests are filtered based on a known IP address. You can specify a mask for an IP address using the asterisk (*). If used, the asterisk must always be the last character of the mask, for example 127.0.0.*, 127.0.*, 127*. URI filters: Requests are filtered based on the URI of the incoming HTTP request. The rules for pattern matching are the same as for matching client IP address filters. Enterprise bean method name filters: Requests are filtered based on the full name of the enterprise bean method. As with IP address and URI filters, you can use the asterisk (*) to provide a mask. The asterisk must always be the last character of a filter pattern. Filter combinations: If both URI or EJB and client IP address filters are active, then Request Metrics require a match for both filter types. If neither is active, all requests are considered a match.

It is important to understand that filters are applied to requests as they enter the appserver from the client (at the Web or EJB container level). Depending on defined filters, the request is either marked to have metrics generated or not marked to mean that no Request Metrics records should be produced for the duration of the request.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.