Request Analysis Dashboard

Felix edited this page Dec 4, 2015 · 2 revisions

You can use the interactive Requests and Call Stacks Dashboard to search and analyze requests.

To enlarge the pictures on this page, right-click on them and select 'Open pricture in new tab' (Chrome) or 'View image' (Firefox).

Open the Dashboard

To open the Request Analysis dashboard, click on Dashboard - Load Saved Dashboard and select Request Analysis

Open Request Analysis Dashboard

This is what you get: request analysis kibana

Klick on the Graphs to apply filters. Filters can be pinned so they are still active if you select a different dashboard or if you select the Discover tab.

Request Details

To inspect request traces, go to the Discover tab and select the 'Request Analysis' saved search. Here you can see details for particular requests you are interested in. If you have pinned the filters from the Request Analysis dashboard only those requests are shown which match the criteria. request trace kibana

If you click on a row, that row will expand and you can see more details about the request. Click on the row again to collapse it.

The following table describes the fields of the detail view.

Field Description
@timestamp The date and time the request entered the server.
application The name of the application that handled the request. This value is obtained from the display-name of web.xml. Alternatively, you can use the stagemonitor.applicationName property of the stagemonitor.properties configuration file.
bytesWritten The amount of bytes that where written into the HTTP response (the response size).
clientIp The IP of the client who initiated the HTTP request.
cpuTime The amount of time in ms it took the CPU to process the request.
error true, if there was an error while processing the request, false otherwise.
exceptionClass The class of the thrown exception. (Only present, if there was a exception)
exceptionMessage The message of the thrown exception. (Only present, if there was a exception)
executionTime The time in ms it took to process the request in the server.
headers The HTTP headers of the request. You can configure, if headers should be collected and which headers not to collect.
host The name of the host of the server that handled the request.
instance The name of the instance of the application that handled the request. The instance name is useful, if you have different environments for the same application (maybe even on the same host). However, it leads to errors if you have a application with the same instance name on the same host. By default, the instance name is the domain name of the server and it is obtained from the first incoming request. You can also choose to set a fixed instance name.
message The stack trace of the request. A more detailed description can be found here.
method The HTTP method of the request.
name The name of the usecase e.g. 'Show Category' or 'View Item Details'.
parameters The query sting of the request. You can obfuscate sensitive parameters.
stackTrace The full stack trace of the thrown exception. (Only present, if there was a exception)
statusCode The HTTP status code of a request.
url The requested URL.