Best Practices for Creating Journal Monitor Groups - ironstream_for_elastic - ironstream_for_splunk - 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 Elastic®
Ironstream > Ironstream Hub
Ironstream > Ironstream for Kafka®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022
ft:lastEdition
2024-04-15
ft:lastPublication
2024-04-15T10:44:03.897025
  • Use the same Journal Monitor Group when there are multiple objects being journaled in the same journal and the entry type(s) and frequency are the same. The journal monitor job will group the objects and will retrieve entries for all objects at the same time, to reduce the number of times the journal is accessed.
  • When a monitored journal is expected to have a higher volume of activity compared to other monitored journals, use a separate journal monitor group for that journal.
  • Lower activity journals should be combined into one journal monitor group to reduce the number of journal monitor jobs.
  • Limit each journal monitor group to no more than five different journals.