Skip to main content
Terminal Services Managerv26.11 · Nov 2026 Download View Pricing

Logging

The Logging page controls how much detail the program writes to its in-memory log (the Application log) and to the on-disk log file.

Preferences, Logging page

Minimum level (in memory)

The General group has one setting:

  • Minimum level - the lowest level kept in the in-memory log. Options: Debug, Info (default), Warning, Error, Fatal. Entries below the threshold are dropped before the log sees them.

Set this to Debug when you need verbose tracing for support; revert to Info for normal use.

File logging

  • Enable file logging - tick to write the log to disk as well as to the Application log. Off by default.
  • Minimum level - the lowest level written to the file. It cannot be lower than the in-memory minimum level, because entries dropped from memory never reach the file. The default is Error.
  • Log path - the directory the log files are written into. A browse button marked ... opens a folder picker.
  • File prefix - the file-name prefix used for each log file. Files are named <prefix>_<yyyymmdd> plus the extension of the format.
  • File format - CSV (default, extension .csv), Text (.log), or JSON (.json).
  • Max file size - rotates to a new file when the current one reaches this size. Range 1 to 1000 MB; default 10 MB.
  • Max files count - how many rotated files to keep. Older files are deleted to stay under the count. Range 1 to 100; default 10.

Validation

OK is refused if the log path or the prefix is empty, if Max file size is outside 1 to 1000 MB, or if Max files count is outside 1 to 100. A message names the setting.

What happens when you change a setting

In-memory level changes apply immediately; the next entry uses the new threshold.

File-logging changes (enable / disable, level, format, path) apply on save: the current log file is closed, and a new one with the new settings is opened. The on-disk content from before the change is left intact.

Was this page helpful?