Skip to main content
Skip table of contents

PLANTA pulse Logger

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:57 UTC 2025","trace":null} Information

  • The PLANTA pulse logger can be configured to document the operation of the software.
  • The related settings are configured in the Meteor Settings.

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:57 UTC 2025","trace":null} Default configuration

  • The following configuration is used when no configuration is defined in the Meteor Settings.
JSON
"logger": {
    "enable": true,
	"path": "logs",
    "transports": {
      "console": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
      "file": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
      "mongodb": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"]
      }
}

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:57 UTC 2025","trace":null} Details

  • de/activates the logger
  • transports: defines where the logs are displayed
    • logs are displayed in the console
    • logs are saved in log files
      • {"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:58 UTC 2025","trace":null} The log files are saved in the /logs directory as long as no other path is defined.
    • logs are saved in the MongoDB
      • {"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:58 UTC 2025","trace":null} 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 troubleshooting
      • 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

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:56 UTC 2025","trace":null} Note

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

{"status":500,"error":"Internal Server Error","message":null,"timeStamp":"Fri Mar 21 11:57:57 UTC 2025","trace":null} Example of a complete log output on all levels:

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


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.