Browse and search documentation

Asset inventory and relationships

Use the asset center to confirm resource identity, ownership and freshness before connecting, inspecting or releasing.

For: Resource administrators and operatorsReviewed:
On this page

Identify the exact resource

Names can repeat and IP addresses can change. Check asset type, project, cloud account, region and resource identifier before acting; do not rely on a name alone.

InformationWhy it matters
Type and sourceDistinguish hosts, databases, cloud resources, applications and services and where their records originated
Project and ownerConfirm access scope and who is responsible for follow-up
Observation or synchronization timeAssess freshness instead of treating an old state as live
Agent statusDetermine readiness for Agent-dependent jobs or diagnostics

Find and check assets

  1. Open the asset center, choose the resource category and narrow the inventory to the relevant project and resource conditions.
  2. Open details and check source, identity, state and last update. For cloud resources, also confirm account and region.
  3. Review related applications, services and resources. Ask an administrator to resolve incorrect ownership or relationships before acting on assumptions.
  4. Open connections, diagnosis or related records from that resource and verify the preselected target on the destination page.

Read relationships and topology

Start a topology investigation with a specific asset, then check both resource types, the relationship source and observation time. Stale relationships, retired resources and relationships awaiting review are not equivalent to current valid ones.

Graph views can have limits; consult the detailed list when only part of the graph is shown. An observed relationship does not establish fault causality or automatically determine cost allocation.

Applications and services

An application represents a business system; a service is an independently deployable unit within it. Register the service under its application in CMDB before binding it in the release module. Matching names alone do not establish that relationship.

When a resource is missing

  • Check project access, category and filters, then verify cloud-account synchronization succeeded for the intended scope.
  • An asset without an online Agent may have been inventoried but not enrolled. Follow Agent onboarding separately.
  • For duplicate names, distinguish sources and identities before deleting or merging anything; incorrect merges affect authorization and targets.
Something differs from your environment?

Send your deployment version, page and a redacted description so we can investigate and update the guide.

weiwendi@aiops.red