All lessons

Asset ↔ CI Sync

Change a field on either side. See which values propagate, which direction they flow, and what breaks the link.

Asset ↔ CI Linked

alm_hardware

ASSET-0001
display_name
serial_number
model
assigned_to
location
install_status
cost
po_number
stockroom
managed_by
owned_by

cmdb_ci_computer

PRODWEB-01
name
serial_number
model_id
assigned_to
location
install_status
ip_address
os
os_version
discovery_source
managed_by
owned_by

Sync Rules

serial_number ↔ serial_numberAsset → CI
Asset is source of truth for serial number — syncs to CI
model ↔ model_idAsset → CI
Model reference syncs from asset to CI when asset model changes
assigned_to ↔ assigned_toAsset → CI
Assignment flows from asset to CI — asset is the assignment authority
location ↔ locationAsset → CI
Location syncs from asset to CI
install_status ↔ install_statusIndependent
Install status is maintained independently — asset and CI can have different values
managed_by ↔ managed_byAsset → CI
Managed by syncs from asset to CI
owned_by ↔ owned_byAsset → CI
Owned by syncs from asset to CI
cost ↔ —Asset Only
Cost is financial data — exists only on the asset, never syncs to CI
po_number ↔ —Asset Only
PO number is procurement data — asset only
stockroom ↔ —Asset Only
Stockroom is an asset lifecycle field — not relevant to CI
— ↔ ip_addressCI Only
IP address is discovered/technical data — lives only on CI
— ↔ osCI Only
OS is discovered data — CI only
— ↔ os_versionCI Only
OS version is discovered data — CI only
— ↔ discovery_sourceCI Only
Discovery source is a CI-side audit field

Sync Log

Pick a scenario or change a field to see sync events.