Log files contain messages about the activity of the Hub main process and all Pipelines in date/time order. They are particularly useful for diagnostic purposes and for use by Precisely Support because they can provide a picture of the actions that Hub has taken.
The number, type and contents of the log files are configured in logsettings.json.
The IBM i Configuration tool also generates log messages. The number, type and contents of the log files generated by the configuration tool are configured in ui_logsettings.json.
The Hub portal also generates log messages. The number, type and contents of the log files generated by the configuration tool are configured in portal_logsettings.json.
If logsettings.json is missing or empty, then Hub will automatically create a User log and a Trace log, both of which will output to stderr on the console.
A logging level of “Verbose” generates a lot of messages. It is not recommended to set log levels to “Verbose” unless you are troubleshooting Hub.