Traffic-Based Service Mapping for vCenter / ESX Hosts — Has Anyone Done This Successfully?

[Ashutosh32]

Hi Community,

We are currently working on building Service Maps for our Hypervisor infrastructure (ESX hosts and VMs) in ServiceNow and have hit a wall — hoping someone here has been down this path before.

Our Setup:

• We have an active vCenter integration in ServiceNow that is successfully bringing in all vCenter instances and everything below them — ESX hosts, VMs, and their relationships — into CMDB
• We are trying to build a traffic-based top-down Service Map starting from vCenter or the ESX hosts

What We Have Tried:

• Created entry points using individual ESX host IPs — resulted in SN-1000 (All patterns failed) and SN-1001 (No pattern found for entry point type) errors
• Confirmed with ServiceNow support that ESX hosts do not run discoverable applications or processes, making traffic-based mapping not possible for ESX directly
• Explored tag-based mapping but were advised it could lead to a dead block

Our Question: Has anyone successfully done traffic-based Service Mapping for vCenter or ESX infrastructure where vCenter integration is already in place? Specifically:

• Did you use vCenter itself as the entry point and if so, what entry point type and configuration worked?
• Were you able to get the ESX hosts and VMs to appear in the service map automatically as child objects
• Any other approach that worked for mapping hypervisor infrastructure beyond manual mapping or dependency/unified maps?
  
  Any guidance, experience, or pointers to relevant documentation would be greatly appreciated!

  Thanks in advance.