Skip to Content

Warning
Helix documentation is moving from docs.bmc.com to docs.helixops.ai

Key pages will redirect to the new domain on May 26, 2026. However, some legacy documentation links will not be redirected. 

In-product help links might not work after migration as we transition and update them within the product.

For any queries, reach out to IX-Support@helixops.ai.

Monitor adapter event deduplication

TrueSight Orchestration provides fault tolerance by enabling an adapter on multiple peers in a grid. When multiple monitor adapters are deployed in a grid to monitor the same source, the event could possibly be captured by one or more instances of the monitor adapter. Event deduplication is achieved by caching a record of each event received for two minutes. This record is then used to detect and reject subsequent duplicate events.

Warning

Note

Deduplication requires all monitor adapter instances of a given type to have the same name.

You can change the event caching interval by setting the value in the tuning-config.xml file as follows:

<config>
  <adapter-manager>
    <event-digest-timeout>120000</event-digest-timeout>
  </adapter-manager>
</config>

By setting the Logging Level to DEBUG for Adapter Framework you can see the following log entries in grid.log:

  • When an event is discarded: AdapterManager : Discarding duplicate event
  • When an event is processed: AdapterManager : ADAPTER_MANAGER: Submitted event to local Activity Processor.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Orchestration Content 20.18.01