Hi Team,
We have observed that some Azure VMs are not getting populated in the CMDB → cmdb_ci_vm_instance table, even though these VMs are active in Azure and should be discovered through Azure Discovery.
🔹 Missing VMs:
VMNPEDCR7SE001 (10.40.3.27)
VMNPSDCR7SE001 (10.60.3.5)
VMNPSDCR7COL001 (10.60.3.6)
VMNPEDCR7COL001 (10.40.3.15)
🔹 Expected:
These VMs should be automatically discovered and populated in CMDB to form relationships with the non-production Application Service (Rapid7).
🔹 Current Setup:
- Multiple Azure discovery schedules exist (e.g. Azure subsc-np-security-001 - VM schedule, Azure subsc-np-connectivity-001 - VM schedule, etc.).
- All schedules are Active = true.
-
🔹 Issue:
Only the above 4 VMs are missing in CMDB, even after Azure Discovery jobs run successfully.
Request for help:
Could anyone please guide:
- How to identify which Azure discovery schedule or subscription is responsible for these specific VMs?
- Any specific logs or tables to check if these VMs were skipped by Discovery or rejected by IRE?
- Any known issue or configuration step that could cause some Azure VMs to be missed during CMDB population?
how to fix this issue can any one please help me here
