Additional Logging for IBM i Sources - Ironstream_Hub - ironstream_for_kafka - ironstream_for_elastic - ironstream_for_splunk - 1.3

Ironstream Hub Administration

Product type
Product family
Ironstream > Ironstream Hub
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Elastic®
Product name
Ironstream Hub
Ironstream Hub Administration
First publish date

IBM i sources can be configured to provide additional LPAR specific log files. See Creating an LPAR-specific log.

The use of LPAR specific logs is provided for backward compatibility and they should only be used as part of investigations into problems. They should not be left running indefinitely. Having multiple LPAR specific logs may result in performance degradation, and for that reason a parameter must be defined in the ihubmain.json file to allow them to be used.

This parameter is HonorLPARSpecificLogSettingsOnRestart.

When first installing Hub or upgrading from a previous version, this parameter is not present, and defaults to false.

A value of false means that, when Hub is started or restarted, no LPAR specific logs will be created even when an IBM i source configuration’s log level is set to a value other than NONE.

The settings that enable LPAR specific logs to be written will only be honored if this parameter is manually entered into ihubmain.json and set to true, as per this example:


This parameter’s value does not change any values in logsettings.json nor any IBM i source configurations, it simply prevents the creation of any LPAR specific logs. It also does not have any effect on messages being written to Hub log files.

Setting HonorLPARSpecificLogSettingsOnRestart to false or removing it from ihubmain.json provides a quick and simple way, without having to update individual IBM i source configurations, to ensure that, next time Hub is started, logging messages will only be written to the Hub application logs.