October 24, 2022 - Release Notes
New Profit Analysis Dashboard Pane in CMx
CloudCheckr is introducing a new pane type called Profit Analysis which allows CMx users to view profit broken down in a variety of customizable ways. CMx users may view their profit by cloud account over a user configured timeline. The total cost is broken down by unblended cost and list cost, while the profit achieved is highlighted. CMx users may filter their results by Service Category and Resource Tags, and configure their preferred chart type.
CMx users with access to both actual (unblended) cost and list cost may build a dashboard consisting of multiple Profit Analysis panes to break down their profit by several key Service Categories, and over various timelines.
Retail Rate Calculation Without A Matching Retail Meter
The process within CloudCheckr for calculating the Retail rate with Azure has been improved. Unfortunately in some cases Azure is not making available a meter and price, resulting in costs ingested with an unmatched Retail Meter being calculated at a rate of $0.
To avoid this situation, when no matching Azure cost can be identified for a given meter to ingested, CloudCheckr is now passing through Azure Standard cost instead. This ensures that no Retail price will be represented at a lower value than the actual cost, helping those customers who invoice or recover costs based on Retail cost type.
Improvements and Bug Fixes
- We are aware of an issue where the Advanced Grouping report crashes in a Chrome browser when generating large amounts of data, given Chrome’s lower memory limit vs other broswers. To work around this limitation, we recommend either using another browser in these large memory use conditions, or ordering the Group By fields with the ‘Location’ field before the ‘Resource Group’ field.
- We fixed an issue where the instance name within the instance details of exported EC2 Cost Details reports were not displayed.
- We fixed an issue where the Hours Running field within History by Virtual Machine displayed an inaccurate value.
- We fixed an issue where the MultiAZ value calculated for an RDS Reserve Instance was incorrect.
- We fixed an issue where Azure Cost savings values reported in MAV were inaccurate under certain conditions.