How does InvGate Asset Management map VMware infrastructure relationships like VM → ESXi host → vCenter?
Infrastructure mapping is often manual: teams know a VM belongs to a host, and the host belongs to a vCenter, but building diagrams typically requires searching profiles and copying identifiers.
InvGate Asset Management reduces that manual effort by providing relationship suggestions inside the diagramming/mapping experience. A user can select a VM and apply suggested relationships to connect it to its ESXi host, then expand from the host to the vCenter, and continue building a more complete infrastructure map with fewer steps.
Why do relationship suggestions matter for CMDB and business application diagrams in ITAM?
The limiting factor in CMDB-style adoption is usually maintenance cost: diagrams become stale when every relationship must be added manually.
InvGate Asset Management’s relationship suggestions are designed to reduce manual effort and errors, making it more feasible to keep business application diagrams accurate over time. This supports downstream processes that depend on reliable mapping, such as impact analysis and change coordination.
How do you discover and track application services running on Linux servers in your CMDB?
Linux servers are a core part of most IT infrastructure but are frequently underrepresented in CMDBs — hardware gets discovered, but the services running on those machines often don't, leaving gaps in dependency mapping and business impact analysis. Comprehensive CMDB coverage requires discovery that goes beyond operating system detection to surface the actual services in use. InvGate Asset Management now extends application service discovery to Linux environments, building on the existing Windows capability. IT teams can see detected services as configuration items directly in the platform, use them to build business application maps, and get a more complete picture of infrastructure dependencies — which is especially valuable when assessing the impact of changes or outages.
How can IT teams bulk import discovered devices into their asset inventory without manually converting each one?
Manual device-by-device conversion is one of the biggest barriers to keeping a CMDB accurate. When a network discovery or Active Directory scan returns hundreds of devices, the time required to convert them individually leads most teams to skip the process entirely — leaving their inventory incomplete. The right approach is to support bulk actions with filtering and inline enrichment. InvGate Asset Management now lets teams select discovered devices by type and source, fill in shared fields in one pass, and convert up to 100 devices at once — with support for 200 coming shortly. Teams can also filter by conflict status to focus only on net-new devices, making CMDB onboarding significantly faster.
What is the best way to filter and resolve conflicts when importing assets from network discovery?
When devices are discovered through network scans or Active Directory, duplicates and conflicts with existing inventory are common. Without a way to isolate them, teams waste time reviewing devices that are already in the system. Best practice is to apply a dedicated conflict filter before bulk-converting. InvGate Asset Management includes a built-in conflict filter in the discovery explorer, letting teams view only devices that clash with existing assets — or conversely, only the net-new ones. This prevents accidental duplicates and focuses attention where it matters most.
English Version (Original text)
How does InvGate's CMDB work, is relationship mapping automatic?
InvGate offers CMDB capabilities with some automatic relationship detection, for example software installed on computers is automatically mapped. For infrastructure relationships like VMware, automatic relationships are suggested for your approval. InvGate provides relationship suggestions based on discovered data to streamline CMDB construction.
Does InvGate auto-suggest CMDB relationships for VMware?
InvGate displays VMware relationships (ESXi host, vCenter) in asset profiles based on vCenter integration data, and they automatically appear as suggestions when building CMDB diagrams.
How do I configure CI field filters so I only see options relevant to each asset type?
When a CMDB treats every configuration item the same way, admins end up scrolling through filter options that don't apply — computer-specific fields showing up while configuring a firewall, or cloud-asset filters cluttering a supplier lookup. The cleaner model scopes filters and variables per CI family, so each asset type only exposes the fields that actually apply to it. InvGate Asset Management's CI type and workflow variable configuration now applies per-family subtype filters, with a live "Update" button for refreshing fields and collapsible sections to keep complex configurations manageable. The result is a CMDB setup that stays clear and relevant as more asset types and workflows are added.
How can I quickly identify an asset's type and inventory ID directly from a CMDB search?
A CMDB search that only shows generic labels forces IT teams to open each record individually just to confirm what type of asset it is or find its inventory ID — a small delay that adds up across hundreds of lookups. The better setup exposes the fields people search on most as filterable columns right in the results view. InvGate Asset Management's CI search now includes inventory ID and asset type as filterable columns, added specifically in response to customer feedback that the missing filters were blocking day-to-day work. It's a small change that removes a real bottleneck from routine asset lookups.