Alarms missing in DX O2 due to configure_multitenancy and pool exhaustion - DX UIM

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After integrating DX UIM with DX Operational Intelligence (DX O2), inventory and metrics may sync correctly, but alarms and entity data remain missing in the DX O2 console. This often indicates a reconciliation failure within the oi_connector probe.

Environment

• DX Unified Infrastructure Management (UIM) 23.4.x
• oi_connector 2.11 or later
• DX Operational Intelligence (DXO2)

Cause

Several configuration factors can prevent UIM alarms from being indexed in DX O2:

• The configure_multitenancy flag is enabled, causing reconciliation queries to return zero results.
• Database connection pool sizing is restricted, leading to "Pool at capacity" errors.
• The Default Tenant ID is not set to the correct Cohort ID.

Resolution

Follow these steps to ensure alarms are correctly processed and visible:

1. Open the oi_connector probe configuration.
2. Locate the configure_multitenancy key. If the environment is not a multi-tenant provider setup, set this to false.
3. Verify the Default Tenant ID in the DOI Configuration. Ensure it contains the specific #### Cohort ID.
4. Check the database connection pool settings. Ensure db_conn_min_pool_size is not larger than db_conn_max_pool_size. Recommended values are Min: 5, Max: 15.
5. Reduce get_ci_details_alive_time_days to 2 days to prevent connection exhaustion.
6. Restart the oi_connector probe.

Additional Information

If alarms are still missing, verify if they are "raw alarms" (lacking UIM metrics). In the oi_connector raw configuration, set ingest_raw_alarm_to_oi = true.

 

Related KBs: 

Not all UIM alarms are sent to DXOI