WAS v8.5 > Monitoring > Monitoring application flow > Get performance data from request metrics

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 you need to enable these filters.

1. Open the dmgr console.

2. Click Monitoring and Tuning > Request Metrics in the dmgr console navigation tree.

3. Click Filters.

4. Click filter type.

5. Select the check box in the Enable field under the Configuration tab.

6. Click Apply or OK.

7. Click Save. We can enable or disable a filter group. If the group is enabled, we can enable or disable individual filters.

Results

The request metrics filters are enabled according to your configuration. For example, if you 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.

You 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
  This topic summarizes how to add and remove request metrics filter.
• Request metrics filters
  Use this page to view a list of request metrics filters.
• Request metrics filter settings
  Use this page to specify filters that define whether or not trace is enabled for inbound requests. Note the filters will only be checked for inbound requests. For intra-process and outbound calls, filters will not be checked. If an inbound request passes the relevant filters, the request will be instrumented as it moves through WebSphere Application Server. If an inbound request does not pass the relevant filters, the request will not be instrumented for its entire code path in WAS.
• Filter values page
  Use this page to specify the values for source IP, URI, web services, JMS, or EJB request metrics filters. When multiple filter values are enabled, a request will pass the filter as long as it matches one of the filter values.
• Filter values settings
  Use this page to specify the values for source IP, URI, web services, JMS, or EJB method name request metrics filters.
• Add and remove request metrics filters
  This topic summarizes how to add and remove request metrics filter.
• Request metrics filters
  Use this page to view a list of request metrics filters.
• Request metrics filter settings
  Use this page to specify filters that define whether or not trace is enabled for inbound requests. Note the filters will only be checked for inbound requests. For intra-process and outbound calls, filters will not be checked. If an inbound request passes the relevant filters, the request will be instrumented as it moves through WAS. If an inbound request does not pass the relevant filters, the request will not be instrumented for its entire code path in WAS.
• Filter values page
  Use this page to specify the values for source IP, URI, web services, JMS, or EJB request metrics filters. When multiple filter values are enabled, a request will pass the filter as long as it matches one of the filter values.
• Filter values settings
  Use this page to specify the values for source IP, URI, web services, JMS, or EJB method name request metrics filters.

Related

Get performance data from request metrics

+

Search Tips   |   Advanced Search