DMI web service activity

NAM Server ► Tools ► Diagnostics ► DMI web service activity

This report presents statistics on the use of the DMI Service. You can use this report to test and verify web service calls.

  • The report is filled with data only upon service access.
  • The content depends on the methods and parameters used to retrieve data.

The report has three tabs:

Overview

The Overview tab includes the following charts:

  • DMI web service by methods
  • DMI web service by status
  • DMI web service server time by time
  • DMI web service hits by time

Click a chart and drill down to focus the report on the selected time or method.

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.

Queries

The Queries tab shows a table of queries by service name and method name.

Tip

Click a service name and select Show executions of this query to display the Details tab for that service.

Web service 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.

Method name (id: methodName)

The name of the method.

Parameter (1) (id: param1)

One of the parameters used in the operation.

Parameter (10) (id: param10)

One of the parameters used in the operation.

Parameter (11) (id: param11)

One of the parameters used in the operation.

Parameter (12) (id: param12)

One of the parameters used in the operation.

Parameter (13) (id: param13)

One of the parameters used in the operation.

Parameter (14) (id: param14)

One of the parameters used in the operation.

Parameter (15) (id: param15)

One of the parameters used in the operation.

Parameter (16) (id: param16)

One of the parameters used in the operation.

Parameter (17) (id: param17)

One of the parameters used in the operation.

Parameter (18) (id: param18)

One of the parameters used in the operation.

Parameter (19) (id: param19)

One of the parameters used in the operation.

Parameter (2) (id: param2)

One of the parameters used in the operation.

Parameter (20) (id: param20)

One of the parameters used in the operation.

Parameter (3) (id: param3)

One of the parameters used in the operation.

Parameter (4) (id: param4)

One of the parameters used in the operation.

Parameter (5) (id: param5)

One of the parameters used in the operation.

Parameter (6) (id: param6)

One of the parameters used in the operation.

Parameter (7) (id: param7)

One of the parameters used in the operation.

Parameter (8) (id: param8)

One of the parameters used in the operation.

Parameter (9) (id: param9)

One of the parameters used in the operation.

Parameters (id: params)

Parameters used in the operation.

Service name (id: serviceName)

The name of the service.

Time (id: begT)

The time stamp of the data presented on the report.

User (id: userName)

The name of the user.

User Agent (id: userAgent)

Recognized type of a browser (client).

Web service log metrics

Avg server time

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

Canceled hits

The number of cancelled 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.

Total server time

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

Details

The Details tab shows a table of executions of a selected query.

Click a service name and select Open administration console to open a call window for that service.

Web service 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.

Method name (id: methodName)

The name of the method.

Parameter (1) (id: param1)

One of the parameters used in the operation.

Parameter (10) (id: param10)

One of the parameters used in the operation.

Parameter (11) (id: param11)

One of the parameters used in the operation.

Parameter (12) (id: param12)

One of the parameters used in the operation.

Parameter (13) (id: param13)

One of the parameters used in the operation.

Parameter (14) (id: param14)

One of the parameters used in the operation.

Parameter (15) (id: param15)

One of the parameters used in the operation.

Parameter (16) (id: param16)

One of the parameters used in the operation.

Parameter (17) (id: param17)

One of the parameters used in the operation.

Parameter (18) (id: param18)

One of the parameters used in the operation.

Parameter (19) (id: param19)

One of the parameters used in the operation.

Parameter (2) (id: param2)

One of the parameters used in the operation.

Parameter (20) (id: param20)

One of the parameters used in the operation.

Parameter (3) (id: param3)

One of the parameters used in the operation.

Parameter (4) (id: param4)

One of the parameters used in the operation.

Parameter (5) (id: param5)

One of the parameters used in the operation.

Parameter (6) (id: param6)

One of the parameters used in the operation.

Parameter (7) (id: param7)

One of the parameters used in the operation.

Parameter (8) (id: param8)

One of the parameters used in the operation.

Parameter (9) (id: param9)

One of the parameters used in the operation.

Parameters (id: params)

Parameters used in the operation.

Service name (id: serviceName)

The name of the service.

Time (id: begT)

The time stamp of the data presented on the report.

User (id: userName)

The name of the user.

User Agent (id: userAgent)

Recognized type of a browser (client).

Web service log metrics

Avg server time

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

Canceled hits

The number of cancelled 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.

Total server time

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