DMI performance

NAM Server ► Tools ► Diagnostics ► DMI performance

Use this report to trace user activity and overall DMI performance, and to see check the DMI load on the system. This report has three tabs:

  • DMI performance
  • DMI report performance
  • DMI performance details

The default set of dimensions and metrics you see on the report belongs to the Web Server Log data view.

Web server log dimensions

Client IP Address (id: cIP)

The IP address of the client.

Content Type (id: contentType)

The string determining the type of the content served by the HTTP server. Example: text/html, text/xml, application/pdf or image/gif.

Data source (id: dataProd)

The name of the data source in case you have configured a number of associated report servers to be used as data sources on the DMI screen.

Hit time (id: begT2)

The actual time of hit occurrence, with 1-millisecond accuracy.

HTTP Method (id: method)

The HTTP method indicator, such as GET or POST.

HTTP Status (id: status)

Status of the HTTP-based software services, transactions, applications, or HTTP servers, depending on the context of the report. There are for status stages:

  • green -- OK,

  • orange -- some entities underperforming,

  • red -- entity below threshold,

  • gray -- entity inactive.

Session Hashcode (id: sessionHashCode)

Session Hashcode

Time (id: begT)

The time stamp of the data presented on the report.

URL (id: url)

This is an actual URL intercepted from the HTTP request.

URL parameters (id: postData)

The data returned (pre-formatted) by the Web server in the POST stream.

User (id: userName)

The name of the user.

User Agent (id: userAgent)

Recognized type of a browser (client).

User Agent Short (id: userAgentShort)

User Agent Short

Web server log metrics

Avg request bytes

The average number of bytes per request.

Avg response bytes

The average response bytes received.

Avg server time

The average server time the server used to generate a response.

Canceled hits

The number of cancel hits.

Hits

The number of subcomponents of error-free operations or transactions. Note that this metric is recorded at the time when the monitored transactions are closed. In case of HTTP, it is when the whole page has been loaded.

Compare "Hits (started)". For example, when a user issues an HTTP Get, this is reported immediately as a "Hit (started)". If this does not result in an HTTP error, it is recorded as a "Hit".

Max server time

The maximum time the Web server used to generate a response.

Processed hits

The number of good hits processed.

Sum of request bytes

The sum of the request bytes.

Sum of response bytes

The sum of the response bytes received.

Total server time

The sum of the total time server used to generate a response.