12.5.3 Changes in the trace collection points of the trace based performance analysis
In Application Server version 11 and Developer version 11, some collection points of the trace based performance analysis were changed or abolished. If the trace based performance analysis functionality was used, replace the event IDs according to the following table.
|
Output source |
Trace collection point |
Event ID |
Level |
|
|---|---|---|---|---|
|
Application Server version 9 and Developer version 9 |
Application Server version 11 and Developer version 11 |
|||
|
Web container (Web server integration) |
Immediately after the acquisition of a request or the completion of the request header analysis |
0x8200 |
0x8236 |
A |
|
Immediately after the completion of request processing |
0x8300 |
0x8336 |
A |
|
|
Web container (In-process HTTP server) |
When a request is acquired or immediately after the completion of request header analysis |
0x8211 |
0x8236#1 |
A/B |
|
Immediately after the completion of request processing |
0x8311 |
0x8336#1 |
A/B |
|
|
Immediately before the reading of data from the Web client starts |
0x8212 |
0x8237 |
B |
|
|
Immediately after the completion of the reading of data from the Web client |
0x8312 |
0x8337 |
B |
|
|
Immediately before the writing of data to the Web client starts |
0x8213 |
0x8238 |
B |
|
|
Immediately after the completion of the writing of data to the Web client |
0x8313 |
0x8338 |
B |
|
|
Redirector |
All collection points |
0x8000 to 0x8104 |
Abolished#2 |
A/B |
- #1
-
In Application Server version 9 and Developer version 9, for level B, more detailed information than level A was output. However, in Application Server version 11 and Developer version 11, the same content is output for level A and level B.
- #2
-
The root application information is output to the access log and request log of HTTP Server. Use those logs for comparison as a substitute.