Please share with the community what you think needs improvement with Cloudability.
What are its weaknesses? What would you like to see changed in a future version?
More documentation with more use case scenarios would be nice. Also, the dashboard needs to include more graphs per team to show what individual teams are spending in a given time period.
The sizing recommendations should be done in longer than two week windows. They should be looking at a whole year's worth of information because we get spikes, and once you are out of that window, it doesn't account for it. It will say that you can save money, but the reality is that it wasn't estimated with a longer running cycle and time slice. Also, if you were able to have a year long look at it, then it would be able to do some type of a linear regression model along with some predictive analytics, and say, "You spent this much this year, so we estimate with your growth rate that this is where you will need to be next year without any new features. Right now, I don't think that they do good predictions at all. Some of their competitor's do offer these predictions, so this is an area for improvement. Therefore, we would like them to have a linear regression, so we can be predictive for budgets, allocations, and the year's follow ups. We also want to have a longer window of analytics with better certainty that our workload will fit the model, not just in a two week window. With containers, corporate doesn't look at a container level to charge adequately, because things get masked.
The API is not well-documented. It is not straightforward and difficult to use. This needs to be improved, as it is very difficult for our developers to develop automation around it. They need to improve their billing data. It seems that sometimes it is not accurate. We have had customers complain that the data they see on the AWS billing dashboard is not reflected (or is very different) from the data that they see in the product. So, there is some discrepancy in the billing reports. I don't know why, but that is one complaint that we see.
There is always room for improvement in education and training. We are not that mature in terms of our automation. It could help us identify where we could optimize in terms of build.
Cloudability needs to be simplified a bit. It can be quite difficult and daunting when some of my colleagues login for the first time. It is difficult to get their particular reports or dashboards set up. It would be interesting if they sort of expanded their rightsizing model. It's doing a good job at the moment, but it doesn't necessarily take into account a lot of edge cases. Thus, if they spent more time on the development of the rightsizing, it would be quite useful.