If the same HCI environment/datastore is categorized correctly in one Aria Operations instance but appears as "Uncategorised" in another, first, compare the inventory and cost configuration between the two Aria Operations environments.
For HCI, Aria Operations derives cost information using discovered server/storage characteristics such as vendor, model, disk size, and the HCI reference library. Not every server or disk model exists in that reference library. When an exact match isn't available, Aria Operations attempts to use the nearest configuration.
Check the following on the affected Aria Operations instance:
- Confirm that the vCenter adapter/collection is healthy and that the datastore, cluster, hosts, and disks are being discovered correctly.
- Compare Operations > Configurations > Cost Drivers between both Aria Operations instances, particularly the Server Hardware/Hyperconverged configuration.
- Compare the active policies and allocation model assigned to the HCI cluster. Cost Driver allocation behavior is policy-controlled.
- Verify whether both Aria Operations instances run the exact same version/build and management-pack versions.
- Allow the next cost calculation cycle to complete after correcting any inventory/configuration differences. Cost calculations run periodically, so newly collected inventory may not immediately appear in Cost Drivers. The daily cost calculation occurring at approximately 9pm local time.
Since one Aria Operations instance already categorizes the same infrastructure correctly, comparing resource properties and Cost Driver configuration side by side should be particularly useful.
Could you share the Aria Operations version/build from both environments, the HCI platform/vendor, and a screenshot of the affected datastore under Cost Drivers? That should help determine whether this is an inventory discovery issue, a reference-library mapping issue, or a configuration difference.