Keep identity durable
Use a stable record ID plus controlled matching signals so renames, IP changes, reassignments, and reimages do not silently split or merge records.
23 fields · Public CSV · No signup
Build endpoint inventory a CMDB can trust.
Record durable device identity, ownership, lifecycle, management state, source provenance, freshness, and exceptions before synchronizing uncertain data into a CMDB.
Record provenance
Name the source system and observation time instead of treating collected facts, assigned ownership, and service context as equally authoritative.
Describe lifecycle honestly
Separate active, temporarily offline, repair, pending retirement, retired, and disposed devices from the management state reported by an agent.
Own uncertainty
Queue duplicate candidates, stale values, conflicting owners, and other exceptions with an accountable owner and next review time rather than guessing.