By default, a new virtual service is configured to provide full client Logs for the first 30 minutes, then drop-down to a reduced logging level by capturing significant logs only. The Full Client Logs option includes any significant logs, custom full log filters, and any logs generated by custom policies or DataScripts. In addition to significant logs, a virtual service may be configured to log all client connections or HTTP requests. See Log Events for a list of error events that may trigger a significant log.Įrrors can be omitted from the significant logs list by editing the analytics profile used by the virtual service.Network errors, such as aborted connections, abnormal latency, or out of order packets.HTTP errors, such as server or Vantage-originated 4xx and 5xx errors.These significant logs may also include entries for lesser issues, such as transactions that completed successfully but took an abnormally long time. NSX Advanced Load Balancer automatically logs common network and application errors under the umbrella of significant logs.

See the Analytics tab of the Create Virtual Service pop-up for configuring, enabling, filtering, and/or disabling client logs. However, you can toggle between old and new log view. Note: Starting with Avi Vantage version 22.1.3, the tech preview of log view is visible. Logs can be useful for troubleshooting and surfacing insights about the end-user experience and success of the application. These logs can be indexed, viewed, and filtered locally within the Controller. Virtual services and pools are able to log client-to-application interactions for TCP connections and HTTP requests/responses.

Tcp log view