Consider a scenario where two Satellite servers are connected to a single account, both syncing their inventories. A host named client1.example.com was originally registered with satellite1.example.com while running RHEL 8.7.

Later, this host was unregistered from satellite1.example.com, registered with satellite2.example.com, and upgraded to RHEL 8.10. However, the old host profile (RHEL 8.7) was not removed from satellite1.example.com.

As a result, when inventory data is synced from both Satellite servers, two entries for the same host are uploaded—each reflecting different OS versions, which is expected behavior. However, without visibility into which Satellite each record was sourced from, it's difficult to accurately identify and manage such discrepancies.

Proposed Solution:
Include the Satellite server name (e.g., satellite1.example.com or satellite2.example.com) in the Data Collector for each host record. This enhancement will enable users to:

• Clearly distinguish between records sourced from different Satellite servers.
• Take appropriate action, such as removing old entries or reconciling data conflicts.

This small addition would significantly improve data clarity and operational efficiency when managing host inventory in multi-Satellite environments.