Diagnostic Logs show detailed information about API requests to your LightWave Client instance. The logs are written to the Escribe file system and may be viewed from the NonStop command line as edit files or viewed in the LightWave Client Console. If you have a large number of logs, the filter can be used to reduce the number of logs listed by entering a partial name of the log that you wish to view. Logs are prefixed with the service name that generated them.

Diagnostic logging is resource intensive and will degrade the performance of all services on your LightWave Client instance. Diagnostic logging should not be enabled on production instances unless necessary.

To view logs:

  1. Enter the name of the subvol that contains the Diagnostic Logs.
  2. The available logs are listed.
  3. Select the log to view.

To delete one of more logs:

  1. Select one or more log entries or click the  icon to select all logs.
  2. Click the icon to open the delete confirmation dialog.
  3. Click Delete to delete the selected logs or Cancel to exit without deleting.

To download a selected log

  1. From the log detail view click the  icon to open the system file browser.
  2. Select a download location for the file and click Save to download the log to a file.

Request Processing Time

The diagnostic log contains request processing time information. This table describes the timing information:

TimeDescription
SerializeThe time between the receipt of the request IPM from the requester application and the completion of serialization of the IPM into the web service request path components, headers, and payload.

Connect

The time between the completion of serialization and the completion of the connection. This includes completing the socket connect and if applicable, completing the SSL handshake. To improve performance, CLIENT uses the HTTP Persistent Connections protocol to reuse connections for multple requests. If a connection was reused, the Connect time will be 0.
RequestThe time between completion of the connection and the completion of the network send of the request. Note that although the completion of the send is indicated by the NonStop TCP/IP process, it does not necessarily mean that the web service has received the entire request. Delays in the network, including one or more proxies, may increase the time required for the web service to receive the entire request.
ResponseThe time between completion of the send and the network receive of the entire response. This includes web service processing time and the time required to transfer the response over the network.
DeserialzeThe time between completion of the network receive and deserialization of the web service response headers and payload into the response IPM that is returned to the requester application.
TotalThe total time between receiving the request IPM and returning the response IPM to the requester application.