Logging

Logging

File output

The application writes logs in the sus*.log file in the Log sub directory. It contains information about all the operations the application is executing, as well as all kinds of information. This includes, but is not restricted to:

• Application bootstrapping and finalization.
• Source initialization.
• Document uploading state and proceedings.
• Statistics over the upload date and time.

Deleting the log file does not affect the application as it will be created with the next information to be logged.

Security considerations: no sensitive data is stored in logs, like passwords of connection secrets. User or document names may be written to provide information about what the application is currently doing or what went wrong.

Administrative issues: it is a good practice to save the logs, as they may provide valuable information when things do not work as expected. The software producer may ask for the logs for supporting purposes.

Warning: make sure the user starting the application has enough permissions for read-write access to the Log folder.

Seq portal output

With the default configuration, the application outputs the logs to Seq. For more information of this output type please check: https://datalust.co/seq/.