Relationship mapping

Turn an asset list into an operational map

A useful CMDB explains how infrastructure, services, people, and suppliers relate, not only which records exist.

Get launch updatesExplore the Living CMDB

The short answer

CMDB relationship mapping connects configuration items so teams can understand dependency and impact. Instead of investigating an isolated server, switch, application, or contract, operators can see the surrounding service context and make better decisions with fewer blind spots.

Dependency context

Show the relationships that help teams understand what may be affected when a component degrades, changes, or becomes unavailable.

  • Service and infrastructure dependencies
  • Upstream and downstream impact context
  • Faster orientation during active incidents

Infrastructure topology

Place connected network resources into a coherent visual model that supports troubleshooting, planning, and communication.

  • Network and physical connection context
  • Readable views for complex environments
  • Clearer conversations between technical teams

Business relevance

Connect technical resources to owners, locations, vendors, and services so the CMDB reflects both engineering and operational responsibility.

  • Ownership and support context
  • Supplier and contract relationships
  • A shared view across IT disciplines

Continue exploring

Continuous discovery

See how a current asset picture supports dependable relationship views.

Learn more

VECTOR topology mapping

Explore network discovery and physical connection visibility.

Learn more

Operations and change

See how relationship context supports incidents, changes, and audits.

Learn more

Frequently asked questions

What is a CMDB relationship?
A CMDB relationship describes how two configuration items are connected, such as a service depending on an application, a device connecting to a network, or an asset being supported by a supplier.
Why are relationships important in a CMDB?
Relationships provide impact and dependency context. They help teams understand what sits around a configuration item and what may be affected by a fault or change.
Is network topology the same as service mapping?
No. Network topology focuses on connected infrastructure. Service mapping adds the applications, owners, suppliers, and business services that depend on that infrastructure. A living CMDB can make both views useful together.

Build operations on a record your team can trust

See how Kovira brings configuration context into everyday IT work.

Get launch updates