A place for Cloudability product users to learn, connect, share and grow together.
Cloudability Rightsizing Explorer
This release introduces the Rightsizing Explorer which enables customers to group, filter and navigate their rightsizing recommendations, allowing them to better understand their opportunities and focus their efforts to maximize returns.
Some of our customers have struggled to find and focus on rightsizing recommendations that are actionable and provide value to their business. It has also been challenging for some customers to gain a business view of recommendations – allowing them to understand trends by teams, organizational units or application, so they can apply more resourcing, and address problems before they become significant.
The Value Brought by Rightsizing Explorer
The Rightsizing Explorer enables you to group existing rightsizing recommendations by dimensions, then displays them onto a Sankey chart- similarly to cost explorer. You can now also apply filters and change the dimensions displayed. Interactive menus on the chart allow you to dynamically navigate recommendations to find areas of opportunity to focus on. Then, you can drill down into a specific area on the chart, and produce the table of recommendations for that node – which will display resource level information. This table of resources is also able to be exported.
Use Cases
Lets say you want understand which of your teams requires additional training and resourcing to address their current rightsizing opportunities... in addition you want to look at the teams processes to ensure additional waste is not created in the future. You simply add the business mapping containing their team names into the Sankey dimensions- then the largest node on the diagram will be the team with the largest rightsizing opportunities.
In another example, you want to understand where in your technology stack you have the most opportunities for rightsizing, so you can improve your provisioning strategy. You quickly and easily add the business mapping for operating systems, and also resource size. Then, say you discover a large number of attached storage recommendations for a particular operating system, and see that there is a large number of recommendations for a specific resource size. You can then change your image and configuration so new deployments will have smaller attached storage, and utilize a smaller resource size by default. This would result in reduced future rightsizing work, and when refreshing existing deployments during patching windows the recommendations would be automatically addressed.