The difference or mismatch in Billing data between Azure / AWS console and CMP Dashboard
- Below is the Dashboard report from CMP and observed 87,764.72 in cost
- Below is the report generated on the AWS Console and observed 87,147.32 in cost
Earlier investigations and probable cause :
- The cost total sometime does not match with the provider's portal, the reason below :
- The data is for the current unfinished month or for a month that just ended.
- The portal may be more up to date due to the lag involved in the instance downloading and processing the data once per day.
- The data is for a long-finished month, there are a few other things to consider.
Current observation and Issue :
- Observed all above probable cause are not the issues and still, we see the difference in high variation.
- Aggregating on the memory and doing many read & write, could lead to more problems.
Steps to Reproduce
- Log on to the instance
- Impersonate with the user who is having access to review Billing Dashboard
- Navigate > Cloud Management > Cloud admin portal > Analyse > Billing
- Billing Dashboard > Observe the cost and note
- Now log in to the AWS / Azure console and verify the cost available.
- There will be a difference between Billing at ServiceNow CMP and AWS / Azure console
- Import cloud_billing_performance_accuracy_fix_v1.xml
- Import enable_azure_rollup_processor.xml for fast Azure report processing.
- This includes the workaround for the case that Azure billing processing is too slow..
- The incoming data will be aggregated as monthly to reduce the # of records to be processed. The daily trend graph will be no longer valid if this updates is applied.
Note : This Workaround is for "London P* " & "Madrid P* " based instances Only.
Procedure to apply the above Workaround
- Log into the instance.
- Impersonate to the user with privileges to modify Cloud Billing schedules and tables.
- Navigate > Cloud Management > Cloud Admin Portal > Analyse > Billing
- Billing Schedules > Make sure no Billing schedules are currently running
- Deactivate all the Cloud Billing schedules.
- Cleanup the Old Billing data completely
- Make sure no previous billing data is available.
- Import the XML files (Provided above in workaround).
- Billing Schedules > Activate all the Billing Schedules.
- Either wait for the Billing schedule to Execute or Execute on-demand Billing Job.
- Verify the Billing data in CMP and Azure/AWS console.
Related Problem: PRB1340282