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": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
"file": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"],
"mongodb": ["INFO", "DEBUG", "ERROR", "FATAL", "WARN"]
}
}
JSON
Details
- de/activates the logger
transports
: defines where the logs are displayed- logs are displayed in the console
- logs are saved in log files
- The log files are saved in the
/logs
directory as long as no other path
is defined.
- 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 troubleshootingDEBUG
: logs with debug informationINFO
: general informationWARN
: information on undesirable states which could potentially cause errorsERROR
: information on errorsFATAL
: 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"]
}
}
JSON