You can get to the Detail page from any page which lists requests: and pages linked from Request Metrics. Clicking the Request Details button by a request or clicking on the url field will take you to a page which contain detailed information about that request.
At the top of the Request Details page you will see a copy of the request line from the page you came from. Underneath that there are at least 5 tabs, plus 1 for each context on that transaction. The Available tabs are as follows:
|Applicable Request Types|
|Web Request, JDBC|
|Properties||Web Request, MongoDB, FRAPI|
|Traces||Web Request, FRAPI|
|Event Snapshot||Web Request|
The Main tab shows general information about a request such as script name, execution time, memory levels and flags.
The Headers tab shows the HTTP headers for the request and response objects.
The Cookies tab takes the Cookie string from the Headers tab and renders it in a more readable format along with other cookie information such as maximum age and whether is it secure.
The JDBC tab will show any queries which have been run by your page. This information is controlled by the storage strategy and other settings found on the JDBC Settings page.
This is a visualization of the properties that are held on the request. ie description, collection, table.
Parent and Children requests for the transaction. This tab will only appear if the selected request has a parent or child transaction.
FusionReactor Ultimate, Developer and Trial Edition includes an integrated low-overhead Java Profiler – which is the perfect tool for identifying poorly performing code in your production environment. The profiler shows the percentage and actual time spent within each method call. When the Profiler is enabled, requests and transactions will be automatically profiled and stored so you can analyze them at your leisure. You can profile any requests or transactions which are running on the JVM – e.g. Tomcat, JBoss, WildFly, Glassfish, Jetty etc. CFML applications can also be profiled. By clicking on individual classes or methods, it is also possible to perform instant de-compilation
If an error is detected, then details of this will be displayed in the Error Details Tab. This will include the error exception details, as well as a stack trace of where the error happened. By clicking on individual classes or methods, it is also possible to perform instant de-compilation
If running in a pure Java environment, you will need to scroll down the page - to the Caused By area - this will display the stacktrace at the point that the error occured.
The trace tab shows a stack trace of the request. Trace can be enabled in JDBC Settings.
The query plan tab shows the result of an explain function running on the query.
Not all JDBC-compliant databases support the retrieval of query plans. Examples of those that do are Microsoft SQL Server, MySQL, MariaDB, Oracle and PostgreSQL.
The following SQL statements are used depending on the database type :
- MariaDB and MySQL
- using 'EXPLAIN EXTENDED'
- using 'EXPLAIN ANALYZE VERBOSE'
- using 'EXPLAIN PLAN' and DBMS_XPLAN.DISPLAY
- MS SQL Server
- using 'SET SHOWPLAN_TEXT ON/OFF'
Query Plan can be enabled in JDBC Settings.
The AMF tabs displays detailed information about any AMF data that has been used as a part of this request. This data is contributed by the FusionReactor AMF Dissector. AMF is typically used for data transfer in Flash Remoting and in Flex-based Rich Internet Applications, as well as those using Flash Remoting For further information, refer to the AMF Dissector Plugin
The AMF Dissector contributes a tree of information to this tab which visualizes the request and (optionally) the response message flow of the application.
This tab displays a list of any FRAPI traces that have been placed on this transaction. These traces can be simple lists or complex maps of information.
Pages instrumented with FusionReactor's API (FRAPI) can contribute messages to this tab.
The Aggregates tab visualizes information contributed in aggregate to the transaction, but (usually) not stored in detail elsewhere. This data, commonly used by the JDBC subtransaction type, is 'rolled up' and stored on the master transaction. It is usually composed of individual contributes from subtransactions.
The Logging tab displays log statements captured by the Log Tracker plugin throughout the lifetime of a transaction. This includes timestamps, logging level, the log message, and any exception that was logged.
The Json Data tab captures the JSON in the post body and response body on the transaction. If the input or output JSON is malformed, the raw data will be displayed. JSON capture is supported for Grizzly and Jersey in both tomcat and non-tomcat deployments.
See Event Snapshot page