Skip to content

Server and application logs

Server logs provide access to registered file logs and Nginx logs. Deployment output is also available directly in the project.

Add a custom log

  1. Open server logs and add an entry.
  2. Enter a description and the actual server log path.
  3. Save and open the entry.
  4. Verify that the contents belong to the correct application and time period.

Search the list by name or path. Update the entry if the log location changes.

Read and maintain

Output loads from the end in pages. Use Older, Newer and Refresh from end. Lines keep their original order; very long lines may continue onto the next page. Search scans up to 4 MB per step, so use Older to find earlier matches. If archival or log scheduling is offered, check which file the action processes first. Clearing log content removes diagnostic information; preserve needed records beforehand.

Removing a custom entry from the list also removes its related archival and scheduling records in the application. Do not confuse it with clearing the file's contents.

Maintenance scheduling offers daily, weekly or monthly periods and an archival option. Open an existing archive from the archive list by time; remove unneeded archives there. Verify the first run and retention of required records after configuration.

Nginx and project output

Nginx logs help diagnose HTTP requests and web server errors. Find Git pull, deployment script and project operation output in project history.

Cannot read a log

Check file existence, path, server availability and permissions. The application may rotate logs to another file. An empty listing does not prove error-free operation.

Remove passwords, tokens and personal data before sending output to support.