PLANTA pulse Logger

Information

• The PLANTA pulse logger can be configured to document the operation of the software.

• The related settings are configured in the Meteor Settings.

Default Configuration

• The following configuration is used when no configuration is defined in the Meteor Settings.

"logger": {
      "enable":true,
      "path":"logs",
      "transports": {
        "console":["TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL"],
        "mongodb":["ERROR", "FATAL"]
      }
    } 

Details

• enable: de/activates the logger

• path: Directory of the log files

• disableConsoleRedirect: Disable the console redirect.

  • The redirect is always active as long as there is a logger configuration and this value is not set to true.

• maxEntries: Maximum number of entries before entries are replaced

  • Default: 5000

• maxSize: Maximum size in byte

  • Default: 25000000

• transports: defines where the logs are displayed

  • console: logs are displayed in the console

  • file: logs are saved in log files

    • The logs are displayed in the /logs directory if no other path was defined.

  • mongodb: logs are saved in the MongoDB

    • The log files are saved in the AppLogs collection.

  • For each of the transports lists of log levels need to be entered as values:

    • TRACE: Detailed logs for finding errors

    • DEBUG: logs with debug information

    • INFO: general information

    • WARN: information on undesirable states which could potentially cause errors

    • ERROR: information on errors

    • FATAL: information on critical errors

Note

• Logs which are saved in the MongoDB can also be viewed in the Administration panel → Application Logs.

Example of a complete log output on all levels:

"logger": {
    "enable": true,
	"path": "logs",
    "transports": {
      "console": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
      "file": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
      "mongodb": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"]
      }
}