Aria Operations pricing not correct, Aria Automation price card shows similar amount total prices in Aria Ops

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Aria Operations 8.18.x, users may observe that tag-based pricing factors (customPropertiesRateFactor) do not apply correctly across all resource types. While storage tags are successfully taken into account, factors for CPU and Memory may be ignored in the final price calculation. This occurs even when the Pricing Card in Aria Automation appears to be configured correctly for all three resource categories.

Environment

VMware Aria Automation 8.18.x

VMware Aria Operations 8.18.x

Cause

The issue is caused by a configuration limitation in the Aria Automation UI and the backend sync to Aria Operations:

• Currently, only one "Charge applies to" item from the dropdown list should be selected for each unique tag (key:value pair) defined under Pricing Cards.

• Because the Automation UI does not restrict using the same key:value pair multiple times for different resources (CPU, Memory, and Storage), the system follows a precedence logic where only the last assigned value is honored.

• In most scenarios, the last value processed is "Storage," causing the CPU and Memory factors to be overwritten or dropped during the sync to the Aria Operations metering engine.

• Using identical tags to charge for multiple distinct resource types is currently not supported.

Resolution

Workaround 1: Unique Key:Value Pairs

Use different tags to allow the pricing engine to distinguish between resources:

• Option A (Different Values):

  • key1:value1 applied to CPU.

  • key1:value2 applied to Memory.

• Option B (Different Keys):

  • key1:value1 applied to Compute.

  • key2:value1 applied to Storage.

Workaround 2: "All Charges" Selection

If the rate factor is the same across CPU, Memory, and Storage, use a single tag entry and select All Charges from the "Charge applies to" dropdown menu.

Additional Information

A Feature Request has been officially opened to enhance this functionality and allow the same tag pair to be used across different resource categories in a future release. Implementation of this feature is subject to the standard product roadmap and approval process.