Measuring data requests (Performance Monitoring Infrastructure Request Metrics)

Why and when to perform this task

Performance Monitoring Infrastructure (PMI) Request Metrics is a tool that allows you to track individual transactions, recording the processing time in each of the major WebSphere Application Server components. The information tracked may either be saved to log files for later retrieval and analysis, be sent to ARM Agents, or both.

As a transaction flows through the system, Request Metrics tacks on additional information so that the log records from each component can be correlated, building up a complete picture of that transaction. The result looks similar to the following:

HTTP request /trade/scenario                ------------------------------> 172 ms
     Servlet/trade/scenario             --------------------------------> 130 ms
         EJB   TradeEJB.getAccountData                              -->  38 ms
              JDBC select                                      ->   7 ms 

This transaction flow with associated response times can help users target performance problem areas and debug resource constraint problems. For example, the flow can help determine if a transaction is spending most of its time in the Web server plug-in, the Web container, the enterprise bean container or the backend database. The response time collected for each level includes the time spent at that level and the time spent in the lower levels. For example, the response time for the servlet, which is 130 milliseconds, also includes 38 milliseconds from the EJB and JDBC. Therefore, 92ms can be attributed to the servlet process.

Request metrics tracks the response time for a desired transaction. For example, tools can inject synthetic transactions. Request Metrics can then track the response time within the WebSphere environment for those transactions. A synthetic transaction is one that is injected into the system by administrators in order to proactively test the performance of the system. This information can help administrators tune the performance of the Web site and take corrective actions should they be needed. Thus, the information provided by Request Metrics might be used as an alert mechanism to detect when the performance of particular request type goes beyond acceptable thresholds. The filtering mechanism within Request Metrics may be used to focus on the specific synthetic transactions and can help optimize performance in this scenario.

Three types of filters are supported:

When filtering is enabled, only requests matching the filter generate Request Metrics data, create log records, and/or call the ARM interfaces. This allows work to be injected into a running system (specifically to generate trace information) to evaluate the performance of specific types of requests in the context of normal load, ignoring requests from other sources that might be hitting the system.

Learn more about Request Metrics by reviewing this section, including:


Related concepts
Performance Monitoring Infrastructure Request Metrics
Application Response Measurement
Performance Monitoring Infrastructure Request Metrics trace filters
Performance Monitoring Infrastructure Request Metrics data output
Adding instrumentation into request metrics flow
Related reference
Example: Generating trace records from Performance Monitoring Infrastructure Request Metrics
Tivoli performance monitoring and management solutions



Searchable topic ID:   tprf_requestmetrics
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tprf_requestmetrics.html

Library | Support | Terms of Use | Feedback