How to Trace and Analyze Events › HTTP Transaction Trace Components Properties › HTTP Servlett Tracing Properties

HTTP Servlett Tracing Properties

Any subclass of HTTPServlet will generate the HTTP Servlett component when one of the methods that implements methods doGet(), doPut(), doPost() or doDelete() is called. Properties that can be filtered in the Transaction Trace Session dialog box list the filter name.

Class

The class that implemented the HTTPServlett class.

CrossProcessData

Specifies a UUID used for correlation and is applicable only to HTTP transaction tracers.

This property will appear only if this component is the root component.

Format: A 32-byte UUID

Communication Method

The communication method used to invoke the transaction. This will always be set to the value HTTP.

Filter: CICS/IMS communication method equals

Method

The called method that was instrumented and which caused the component to be inserted.

Values

• doGet
• doPut
• doPost
• DoDelete

SeqNoCrossProcessData

Specifies the sequence ID of the correlation UUID.

This property will appear only if this component is the root component.

Trace ID

Specifies the trace identifier, a unique value generated for each trace event

This property will appear only if this component is the root component.

Trace Type

Specifies the transaction trace type.

This property will appear only if this component is the root component.

Normal

A normal trace taken during a transaction trace session.

Alternately, a trace that correlates with a sample from another agent.

Sampled

A sample trace taken because sampling is set. Sample trace appears in the Transaction Trace Viewer pane as correlated traces.

URL

Indicates the URL of the servlet. The leading protocol specifier, computer name, and port number are not included.

Example: /HTTPTest/servlet/FrontEndClient

Filter: URL (from dropdown menu)