Diagnostic Logs show detailed information about API requests to your LightWave Server instance. 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 Server instance. Diagnostic logging should not be enabled on production instances unless necessary. Use of the Auto-disable timer option is strongly recommended to ensure that Diagnostic logging is not left enabled indefinitely.
Diagnostic Logging is disabled by default. To manage Diagnostic Logging, select Diagnostic Logging from the sidebar menu.
To enable or disable logging:
- Click the icon to open the Log Settings dialog.
- Select or deselect Enable Logging
- If enabling logging, set the auto disable timer to automatically disable logging after a defined number of minutes.
- If desired, enter an HTTP status code filter range. Only requests with status codes in the specified range will be logged.
- If desired, configure Log Content Selection. Excluding the HTTP body or server IPM can reduce the size of the log when this information is not of interest.
- Select the services for logging from the list of deployed and enabled services.
- Click Save to update the settings or Cancel to exit without updating.
To delete one of more logs:
- Select one or more log entries or click the icon to select all logs.
- Click the icon to open the delete confirmation dialog.
- Click Delete to delete the selected logs or Cancel to exit without deleting.
To download a selected log
- From the log detail view click the icon to open the system file browser.
- 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:
|The time between the acceptance of the socket connection and the completion of the TLS handshake, if any. If a connection was reused, the Connect time will be "N/A".|
|Request||The time between completion of the connection and the completion of reception of the entire web service request from the network.|
|Deserialize||The time between completion of request reception and the completion of deserialization of the web service request headers and payload into the application server request IPM.|
|Server I/O||The time taken by the application server I/O. For process servers, this includes the time for server OPEN, if necessary.|
|Serialize||The time between the completion of the server I/O and the completion of the serialization of the server reply IPM into the web service response headers and payload.|
The time between completion of serialization and he 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 client has received the entire response. Delays in the network, including one or more proxies, may increase the time required for the web service client to receive the entire request.
|Total||The total time between receiving the request from and returning the response to the web service client.|