Azure Probe: Separate Alert Polling from Inventory Discovery (Enhancement Request)
search cancel

Azure Probe: Separate Alert Polling from Inventory Discovery (Enhancement Request)

book

Article ID: 443875

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Currently, in the DX UIM azure probe (v3.21 and earlier), Azure Monitor Alert polling is coupled with inventory discovery and resource metric collection. This design prevents users from running high-frequency alert polling (e.g., 60 seconds) without also triggering frequent inventory discovery, which can lead to Azure ARM API throttling and probe instability.

Environment

  • DX UIM 23.4.*
  • Azure probe: 3.21 and earlier

Cause

The current probe architecture does not provide a native configuration toggle to isolate alert polling from the broader discovery and collection cycles.

Resolution

Broadcom Engineering and Product Management have accepted this requirement as a formal Enhancement Request (ER).

Workaround / Next Steps:

  1. Enhancement Tracking: This feature is tracked under Feature F166697: Ingest Azure alerts to DX O2 via ODC and the community idea: Azure probe: Separate Azure Alert polling from inventory discovery.
  2. Future Release: The requested functionality—allowing independent configuration for alert polling intervals and the ability to disable discovery—is planned for a future release of the azure probe.
  3. Current Configuration: Until the enhancement is released, it is recommended to increase resource-level intervals (e.g., to 900s) to mitigate API throttling, though a true "alerts-only" mode is not yet available.