Data we can collect with request metrics
Components of the enterprise application can be hosted across several nodes in a distributed system. For example, servlets on one node, EJBs on which these servlets depend on a different node. When a request comes to a process, the process might send the request to one or more downstream processes...
Trace records can be generated for each process with associated elapsed times for that process and correlated together to build a complete picture of the request flow through the distributed system.
We can view the process response time that is monitored by request metrics through...
- ARM interface
- system log files
When a request is sent to the appserver, request metrics captures response times for the initiating request and any related downstream invocations. Request metrics are instrumented in the following components as the request, for example, transaction, travels through the Web server, Proxy Server and the appserver:
- Web server plug-in
- Proxy Server. Instrumented as servlet and Web services requests.
- Web container. Including servlet and servlet filters
- EJB container
- Java DataBase Connectivity calls.
- J2EE Connector Architecture
- Web services. Both on the server and the client side
- JMS engine
- Service Integration Bus
- Portlet container. Including the portlet requests
- Asynchronous Beans.
Select which components to instrument. For example, if we want instrumentation data only for the Web container and the JMS API, select this data in the admin console and the detailed instrumentation data is generated only for the components that you select. The edge transactions are traced for the other components that are not specified for instrumentation.
When filtering is enabled, only requests that match the filter generate request metrics data, create log records, or call the ARM interfaces. You can add work 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 affect the system. If the request matches any filter with a trace level greater than None, trace records are generated for that request.
Related tasks
Monitor application flowWhy use request metrics?
Getting performance data from request metrics