Request Metrics data output

Data in the trace record output file has this format:

PMRM0003I: parent:ver=n,ip=n.n.n.n,time=nnnnnnnnnn,pid=nnnn,reqid=nnnnnn,event=nnnn
- current:ver=n,ip=n.n.n.n,time=nnnnnnnnnn,pid=nnnn,reqid=nnnnnn,event=nnnn
    type=TTT detail=some_detail_information elapsed=nnnn bytesIn=nnnn
    bytesOut=nnnn

The trace record format consists of two correlators: a parent correlator and current correlator. The parent correlator represents the upstream request and the current correlator represents the current operation. If the parent and current correlators are the same, then the record represents an operation that occurred as it entered WebSphere Application Server.

To correlate trace records for a particular request, collect records with a message ID of PMRM0003I from the appropriate server logs. Records are correlated by matching current correlators to parent correlators. The logical tree can be created by connecting the current correlators of parent trace records to the parent correlators of child records. This tree shows the progression of the request across the server cluster.

The parent correlator is denoted by the comma-separated fields that follow the keyword parent:. Likewise, the current correlator is denoted by the comma-separated fields that follow current:.

The fields of both parent and current correlators are as follows:

• ver: The version of the correlator. For convenience, the version is listed in both the parent and current correlators.
• ip: The IP address of the application server node that generates the correlator.
• pid: The process ID of the application server that generates the correlator.
• time: The start time of the application server process that generates the correlator.
• reqid: An ID assigned to the request by Request Metrics. This ID is unique to the application server process.
• event: An event ID assigned to differentiate the trace events.

The metrics data for the timed operation is listed after the parent and current correlators:

• type: A 3 character code that represents the type of operation that is traced. Values include HTTP, URI, EJB, and JDBC.
• detail: Identifies the name of the operation.
• elapsed: The measured elapsed time in units for this operation, including all sub-operations that this operation calls.
• bytesIn: The number of bytes from the request received by the Web server plug-in.
• bytesOut: The number of bytes from the reply sent from the Web server plug-in to the client.

The type and detail fields identify the operation:

• HTTP: The Web server plug-in generates the trace record. The detail is the name of the URI used to invoke the request.
• URI: A Web component generates the trace record. The URI is the name of the URI that invokes the request.
• Enterprise bean: The fully qualified package and method name of the enterprise bean.
• JDBC: The values select, update, insert or delete for prepared statements. For non-prepared statements, the full statement can appear.