Configuring Hub Logging - Ironstream_Hub - ironstream_for_kafka - ironstream_for_elastic - ironstream_for_splunk - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream Hub
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Elastic®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022

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.

There are three log settings files:
  1. The Hub service’s log files are configured in logsettings.json.
  2. The Hub Portal (the browser part) logs are configured in ui_logsettings.json.
  3. 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.