Debug Logging

When using support channels to report issues with the application, it is generally useful to send along meaningful debug logs.

This will improve fixing times and the general quality of the application.

A debug log can contain information about user actions and, in some cases, call stacks generated when exceptions are thrown. Log files are stored for as long as 7 days.

Setting what to log in the debug file

You can set how and what the debug log file records using the settings from File > Options > System > Debug Logging.

By default, debug logging is not enabled, but when you find it necessary, you can enable it temporarily or indeterminately.

Choose the type of information to log in the debug file:

PageDescription
CommandsSDL Passolo records all of the user's operations. An operation is, in this context, any action that is invoked from within the ribbon accessible commands. i.e. as long as such a command is listed in ribbon, it does not matter if it is directly called from the ribbon or with a shortcut key.
Translation HelperPassolo records all translation requests from Passolo and all responses from the add-ins that are able to retrieve translations.
Passolo ShutdownLogs the processes that take place during application shutdown. It could be used to decide if Passolo closed peacefully or not and what problems occurred during shutdown.
ExceptionsThis option is reserved for later use and momentarily does not influence in any way the debug log file.

Apart from these user selectable log items, Passolo logs all the messages displayed in the Messages window.

If a logged error occurs in a .Net add-in, and if the error is caused by an exception, the call stack of that exception is displayed in the Messages window and logged accordingly.

Viewing and managing debug log files

You can view and manage debug logs with the Passolo Debug Log Viewer. To open it, click the Debug Log Viewer link.