/
Debugging Logs for the Editor Application

Debugging Logs for the Editor Application

For debugging purposes, the following log files are available for the Editor Application on the server. Additionally, these logs can be configured to be forwarded to a central logging service such as Fluentd, Logentries, Sumo Logic, etc.

  1. Session Logs:

    • Location: /var/log/wt/editor.log

    • Description: Contains session logs specific to the Editor Application.

  2. WT Logs:

    • Location: /var/log/wt/wt.log

    • Description: Contains logs related to the WT framework, which the Editor Application may utilize.

  3. Nginx Access Log:

    • Location: /var/log/nginx/access.log

    • Description: Access log for the Nginx proxy server, providing information about incoming requests to the Editor Application.

  4. Nginx Error Log:

    • Location: /var/log/nginx/error.log

    • Description: Error logs for the Nginx proxy server, containing information about any errors encountered while processing requests for the Editor Application.

By referring to these log files, you can diagnose issues, monitor activity, and troubleshoot any errors or unexpected behavior within the Editor Application running on the server. Additionally, integrating these logs with a centralized logging service can facilitate easier management and analysis of log data.

Related content

Executable parameters
Executable parameters
More like this
Crash Reporting Configuration
Crash Reporting Configuration
More like this
Cloud Crash HTTP Endpoint
Cloud Crash HTTP Endpoint
More like this
Token Authentication
More like this