10.3.2 Trace collection points of the web container

The following explains the details of the trace collection points of the web container.

When synchronous processing is used

The following shows the trace collection points of the web container.

Figure 10‒1: Trace collection points of the web container (in synchronous processing)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.

#:

If any application information is included in the request header, the application information is inherited.

If no application information is included, application information will be generated.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒3: Details on the trace collection points of the web container (when synchronous processing is used)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB100	1	Standard level	Immediately after the completion of request collection and request header analysis	HTTP method name	URI	-
0xB101	6	Standard level	Immediately after the completion of request processing	HTTP method name	URI	In a normal state Status code In an abnormal state Status code: exception name
0xB200	2, 3	Standard level	Immediately before calling a servlet, JSP, JAX-RS, or JAX-WS	For something other than JSP Class name For JSP JSP file path that begins at the context root	-	Session ID
0xB201	4, 5	Standard level	Immediately after the completion of servlet, JSP, JAX-RS, or JAX-WS processing	For something other than JSP Class name For JSP JSP file path that begins at the context root	-	In a normal state Session ID In an abnormal state Session ID: exception name
0xB202	3	Standard level	Immediately before calling static content (DefaultServlet)	-	Context root name	Session ID
0xB203	4	Standard level	Immediately after the completion of static content processing (DefaultServlet)	-	Context root name	In a normal state Session ID In an abnormal state Session ID: exception name

When asynchronous processing is used

The following shows the trace collection points of the web container when responses are sent by asynchronous processing of servlet.

Figure 10‒2: Trace collection points of the web container (when asynchronous processing is used)

Reference note: This figure shows the workflow for collecting traces as an extension of a request. This figure does not show all the triggers to collect traces. Other triggers for collecting traces exist.

#:

If any application information is included in the request header, the application information is inherited.

If no application information is included, application information will be generated.

The following table lists event IDs, trace levels, trace collection points, and information that can be collected.

Table 10‒4: Details of the trace collection points of the web container (when asynchronous processing is used)
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Information that can be collected
Event ID	Number in the figure	PRF trace collection level	Trace collection point	Interface name	Operation name	Option
0xB100	1	Standard level	Immediately after the completion of request collection and request header analysis	HTTP method name	URI	-
0xB101	6	Standard level	Immediately after the completion of request processing	HTTP method name	URI	In a normal state Status code In an abnormal state Status code: exception name
0xB200	2	Standard level	Immediately before calling a servlet, JSP, JAX-RS, or JAX-WS	For something other than JSP Class name For JSP JSP file path that begins at the context root	-	Session ID
0xB201	5	Standard level	Immediately after the completion of servlet, JSP, JAX-RS, or JAX-WS processing	For something other than JSP Class name For JSP JSP file path that begins at the context root	-	In a normal state Session ID In an abnormal state Session ID: exception name