workload-discovery-on-aws
workload-discovery-on-aws copied to clipboard
Inaccurate cost information
If your issue relates to the Discovery Process, please first follow the steps described in the implementation guide Debugging the Discovery Component
The estimated cost in workload discovery is roughly double the actual billed amount. I have tested this across four different accounts and I am currently on version 2.0.3.
To Reproduce Steps to reproduce the behavior:
- Follow the instructions to set up the costing feature and bucket replication
- Log into the Workload Discovery console
- Go to "Costs"
- Select an account ID
- In "Cost Data Time Period" enter the timeframe for the entire last month
- Note the Estimated Cost (In my case 6699.76)
- Login to the corresponding account
- In the AWS console navigate to the billing console
- Go to "Bills"
- In the upper-right corner select the previous month
- The returned bill will be very different from the estimated cost (In my case 3365.10)
Expected behavior I expect the estimated value to be closer to the actual billed amount
Screenshots If applicable, add screenshots to help explain your problem.
Browser (please complete the following information):
- Name chrome
- Version 115.0.5790.110
Additional context Add any other context about the problem here.
Hi there, I have tried reproducing this on the latest version of our code base and have been unable to. The code for the cost feature has changed a bit for the upcoming release (v2.1.0) so it may have been fixed by that. We are aiming to release by the end of Q3 but this date could slip. I will update this ticket when the release has happened to let you know.
We fixed several bugs in the cost feature in v2.1.3 that was released yesterday, I wonder if that might fix this issue.
@svozza the costs still look to be quite off. I was hoping maybe it's the Savings Plans or Enterprise Support costs, but subtracted from the account total, the remainder is less than Workload Discovery displays for costs. Any thoughts on what would account for the discrepancy?
Screenshots attached:
Sorry, I didn't see this reply. The solution doesn't take savings plans into account, could that be the cause of the discrepency?
Hi gitcdb please take a look at the the above question and let us know. If we don't hear from you soon I will close the issue, thanks.