Phase 5: Job Log Forwarding - ironstream_for_elastic - ironstream_for_kafka - ironstream_for_splunk - 7.4

Ironstream for Splunk®/Kafka®/Elastic® for IBM i Ironstream Integration Components Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Elastic®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream for Splunk®
Version
7.4
Language
English
Product name
Ironstream Splunk®/Kafka®/Elastic®
Title
Ironstream for Splunk®/Kafka®/Elastic® for IBM i Ironstream Integration Components Administration
Copyright
2022
First publish date
2007
Last updated
2023-08-25
Published on
2023-08-28T08:26:48.055356

You can filter messages from IBM i job log and forward them to your chosen destinations. To do that, Ironstream Proxy Server must receive Job End message (CPF1164) at first then request collection of the job log by the Ironstream agent. You can choose which jobs to collect the logs and which messages from the logs to collect each LPAR using the Configuration Tool.

Following are the pre-requisites that are needed before job logs can be collected and forwarded to a chosen destination:

  1. The jog logs must be going to the system QEZJOBLOG in the QUSRSYS Library.

  2. QHST must be collected from the LPAR.

  3. The CPF1164 message must be included in the QHST message filter list.

  4. Any changes to the QHST collection need to be distributed to the LPARs.

  5. Any changes to the Job Log Forwarding Filters need to be distributed to the LPARs.

See Phase 3: Add, Modify, and Distribute Message Queues and Message IDs section for details on how to configure the QHST collection.

Once the Ironstream Proxy Server receives a CPF1164 message for a job that is listed in a Job Log Forwarding filter associated with an LPAR, the Proxy Server requests the log from the agent after giving the following parameters:

  • Job Name

  • Job ID

  • Job User

Then, the agent sends the records that meet the message filtering constraints. The Ironstream Proxy Server processes these raw records, creates JSON formatted records and sends them to the destination.