Isolating performance for specific types of requests
This topic describes how to enable request metrics filters.
Request metrics compares each incoming request to a set of known filters, but we need to enable these filters.
Tasks
- Open the administrative console.
- Click Monitor and Tuning > Request Metrics in the administrative console navigation tree.
- Click Filters.
- Click filter type.
- Select the check box in the Enable field under the Configuration tab.
- Click Apply or OK.
- Click Save. We can enable or disable a filter group. If the group is enabled, we can enable or disable individual filters.
The request metrics filters are enabled according to the configuration. For example, if we enabled source IP, only requests whose source IP matches the one specified in the filter will be instrumented.
Filters will only be checked for edge transactions. An edge transaction is the transaction that first enters an instrumented system. For example, if a servlet calls an Enterprise JavaBean, the servlet is the edge transaction, assuming it is not instrumented at the web server plug-in, and the URI and SOURCE_IP filters will be checked for the servlet request. However, when the request comes to EJB container, EJB filter will not be checked because it is no longer an edge transaction.
What to do next
We must regenerate the web server plug-in configuration file as described in the Regenerating the web server plug-in configuration file topic after modifying the request metrics configuration.
Subtopics
- Add and remove request metrics filters
- Request metrics filters
- Request metrics filter settings
- Filter values collection
- Filter values settings
Get performance data from request metrics