Age Limit for Journal Monitoring - 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

Each Journal Monitor job stores the sequence number of the last record it collected from a journal. On starting a Journal Monitor it uses this sequence number to ensure it does not send entries twice, but it also checks the timestamp to ensure the entries are within a configurable Age Limit. Only if an entry’s sequence number is after the saved sequence number and its timestamp is within the Age Limit is an entry collected. This protects you from sending a large volume of historic data when the Agent starts, if the old data is not required.

By default, this Age Limit is set to 0 seconds, which means that no records journaled while the agent is stopped are collected. This value can be set to any number of seconds and we recommend that you set it to at least 1 day (86400 seconds). This ensures that, if the agent is stopped then restarted after a relatively short period, there will be no gaps in data collected.

To set this value take these actions (currently it cannot be set in the Configuration Tool):

  1. On the Proxy Server go to the conf folder:

On Windows: \EView Technology\EView400i\conf\

On Linux: /etc/opt/OV/share/conf/

  1. Open each System config file, named ev400_config_systemname.For example: if the System is called test then the file will be called ev400_config_test.

  2. Add this line to the bottom of the file, or if the line is already present, edit the existing value. This example sets the limit to 1 day:

EV400_JRN_AGE_LIMIT 86400

  1. Save the changes to the file.

  2. Make sure you Distribute the updated System configuration to each IBM i LPAR affected, after making the change.

Note: This value will persist even if you modify the System configuration in the Configuration Tool.