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 Hub service’s log files are configured in
logsettings.json
. - The Hub Portal (the browser part) logs are configured in
ui_logsettings.json
. - The Hub Portal service (the back-end to the browser) logs are configured in
portal_logsettings.json
.
If any of these log settings files are missing or empty, then Hub will automatically create a User log and a Trace log for that log type, both of which will write to ‘stderr’, normally to the console. If running as a service this ‘console output’ may not be visible, so you are advised to ensure the log settings all contain suitable definitions to write to files.
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.
Hub in zCX Container
If you are using the zCX version of the Hub, you must use the docker cp command to copy the log settings files.
docker cp ironstream-hub-portal:/opt/ihub/conf/logsettings.json
docker cp logsettings.json ironstream-hub:/opt/ihub/conf/logsettings.json