Logging and How it Works

Follow

Updated:

In the table below, you can find the log name and its detailed description.

Log

Description

ndMailApplication.log

Log exceptions that occur in the ndMail application. Includes exceptions’ stack traces. These logs are always system-created, and they do not depend on user’s settings.

ndMailOutlookAddIn.log

Log exceptions that occur in the ndMail Outlook add-in. Includes exceptions’ stack traces. These logs are always system-created, and they do not depend on user’s settings.

ndMailOutlookAddInTrace.log

Tracing logs in the ndMail Outlook add-in. These logs include time of execution, duration, and method parameters of the add-in. These logs depend on the TracingEnabled registry. (HKEY_CURRENT_USER\SOFTWARE\NetDocuments\ndMail). The default value is set to False. Users need to modify it to True.

ndMailApplicationTrace.log

Tracing logs in the ndMail application. These logs include time of execution, duration, and method parameters of Tray Application. These logs depend on the TracingEnabled registry. (HKEY_CURRENT_USER\SOFTWARE\NetDocuments\ ndMail). The default value is set to False. Users need to modify it to True.

ndMailApplicationRESTApiTrace.log

REST API trace – logs interactions with REST API. Shows request, response, time, duration, and request parameters. These logs depend on the RestTracingEnabled registry. (HKEY_CURRENT_USER\SOFTWARE\NetDocuments\ndMail). The default value is set to False. Users need to modify it to True.

ndMailApplicationJournal.log

Logs that have information about the start/stop/connection lost/restored activities. Also, include key operations like: email filing started, email filing finished, and so on.

Back to Top

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk