igloo-core-service’s logging is configured via command line arguments, not config.json.
Options and defaults
Console log level -
--console-log-level debugFile log level -
--file-log-level infoMaximum age of log files (in days) -
--file-max-age 7
Log levels are, in order: debug, verbose, info, warn, and error. Setting a log level will log anything with that priority or higher (e.g. by default the logfile will contain all info, warn, and error messages).
Log files are located in C:\igloo\igloo-core-service\logs\. Log files are rotated daily, and any files older than the configured number of days are deleted.
New files are not created on service restarts; there’s just one per day.
Logs may appear out-of-order in logfiles, so may need to be sorted if this matters. e.g. for Notepad++ - Edit → Line Operations → Sort Lines Lexicographically Ascending.
Configuration with nssm
The service is registered, managed, and started using nssm. Command line arguments provided to the service when it starts should be configured there, using the nssm.exe executable in the service’s installation folder.
Open an administrator command prompt in the service’s install folder (
C:\igloo\igloo-core-service\).Run
nssm.exe edit igloo-core-serviceAdd or change command line arguments as required, e.g.
Arguments may not be present in the text input; just add them.
Click “Edit service” to save changes.
Restart the service via any of the usual means (
services.msc, task manager).
New logging settings will be used.e
Note: It doesn’t make sense to adjust --console-log-level via nssm, as the console isn’t visible.