Pricing Policy is not reflecting the rate-based changes and data in the report is not accurate

Products

• VMware Aria Suite

Issue/Introduction

After making rate-based changes under the Chargeback Billing - VC Pricing policy, the OOTB dashboard "Chargeback (VM Price)" does not reflect the changes.

The report also does not reflect the correct data.

Environment

Aria Operations 8.18

VMware Aria Operations Chargeback

Cause

The vCenter (VC) Pricing is being applied to VM Folders.

Report data values will use the previous pricing up to the date of pricing policy change.

Resolution

1. The pricing policy should be assigned to clusters or vCenters, not directly to VM Folders. See details in Hierarchy of Pricing Policy.

2. Changes made to the pricing policy will take 24 hours to take effect. See How Is Price Calculated.

3. Pricing policy tuning only affects price calculations starting from the day when the tuning is applied.

For example, if tuning were performed on 9/2, the adjusted pricing values would apply from 9/2 onward. However, the price for 9/1 would still reflect the previous policy settings.

If a report is generated based on a view that sums up all the price points for a VM over the period, such as the start of the month (9/1), the report will include tuned prices from the 2nd to the current day, but also one data point using the old pricing policy for 9/1. As a result, the overall VM price in the report will not fully align with the current pricing policy settings.

Moreover, if the policy is modified later in the month, more time is needed to ensure consistency across all data points. For example, if the policy is tuned on August 25th, the monthly report for August would be based on data generated under two pricing rules: One before August 25th and one after. However, if no further changes are made, the report for September will reflect consistent data across the entire month.