Creating an LPAR-specific log - Ironstream_Hub - 1.3.2

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream Hub
Version
1.3.2
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
Topic type
Administration
First publish date
2022

As well as the standard Hub logs, when troubleshooting issues with a specific IBM i LPAR, there is an option to create log files that just include the events from a pipeline for that IBM i LPAR.

In <Configuration Directory>/ihubmain.json, enter/update the key/value pair:

"HonorLPARSpecificLogSettingsOnRestart":true

When Hub is restarted then a log file will be created for each LPAR according to the log level and log size settings specified in the IBM i Configuration Tool. A log level of “Debug” in the configuration tool corresponds to a level of “Verbose” in Hub. See Additional logging for IBM i sources for more details.

If LPAR-specific logging is being honored, then changes to the logging level that:

  • Persist after the pipeline is restarted can be made via the configuration tool. The pipeline needs to be restarted for the change to take effect.
  • Are temporary, and are lost when the pipeline is restarted, can be made via the Hub Command Line Application. The change is immediate. The pipeline does not need to be restarted.

Permanently changing the logging level of an LPAR

  1. Open the Configuration Tool on the Systems tab.
  2. Click Edit for the LPAR you wish to update.
  3. Set the Log Level and click Save.
  4. Stop and Restart the pipeline for this LPAR.

Temporarily changing the logging level of an LPAR

To change the log level of an LPAR to debug level until the pipeline is stopped:

  1. Log on to system running Hub.
  2. Open a command prompt.
  3. Go to the bin folder under the Hub installation path and enter:

    ihubcmd -enable-tracing -pipeline-name <pipeline_name>

To change the log level of an LPAR to info until the pipeline is stopped:

  1. Log on to system running Hub.
  2. Open a command prompt.
  3. Go to the bin folder under the Hub installation path and enter:

    ihubcmd -disable-tracing -pipeline-name <pipeline_name>

Note:
  • These requests are ignored if the Log Level is currently set to None.
  • The logging level will revert to the value defined in the Configuration Tool when the pipeline is restarted.
  • These requests will take effect straight away. There is no need to restart the pipeline.