Creating an LPAR-specific log - ironstream_for_splunk - ironstream_for_elastic - ironstream_for_kafka - Ironstream_Hub - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream Hub
Ironstream > Ironstream for Elastic®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub 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, a log file will be created for each LPAR according to the log level and log size settings specified for the Source in the 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 persists after the pipeline is restarted can be made via the Hub Portal. The pipeline needs to be restarted for the change to take effect.
  1. Open the Hub Portal on the Pipelines page.
  2. Click on the Pipeline that has the Source you wish to update, then click on the Source node in the canvas.
  3. Move to the Log tab and set the Log Level, click Save then Exit to return to the Pipelines page.
  4. Stop and Restart the Pipeline you changed.