I would like the API functionality to improve. As a developer, I've found that the APIs could be more robust, providing insufficient information for effective automation efforts. Additionally, regarding memory metrics, the user interface (UI) seems rudimentary, especially compared to AWS. The UA doesn't align precisely with AWS; compared with AWS CloudWatch, it appears outdated. Enhancements in these aspects would significantly improve the overall user experience. Lastly, the update time after uploading data could also be improved.

Cloudability needs to focus on more cloud providers. 

The only problem with Cloudability we are running is, we have the consultants here who implemented and now their contract is going to end. It already actually ended in December. They are rolling out the knowledge transfer to our teams internally. The way they did it, we are involved now, and it's more like manual work, which we don't like. Cloudability is an external tool, a third-party tool. We would like it to work as a connection to Azure itself and get all the data.

Right now, what we're doing is we are manually putting the data in it, which is something which we don't like about Cloudability. When we talked to the consultant himself, he said, "It's due to how our company's way of working and doing the chargeback." It's complicated and we have to do this manual process. That's the only reason, I was looking for other options. There might be a tool that can provide everything without doing manual work.

I'm not sure if any features are missing per se as we are just really starting to use the solution and we need to dig in deeper to take in all of its functionality.

They can improve the custom range of the network. Now they have just a one-year dashboard. 

I wish there had been a way to temporarily remove certain recommendations from the list for teams that couldn't implement them immediately.  Cloudability could have offered more automation functionality and enhanced the cost allocation modeling, although I understand it is there now!

Cloudability needs to improve on data collection from cloud sources. 

I don't exactly remember the problem with Cloudability. I can say that in my previous company, we could not efficiently make appropriate changes to the tags or resources in Cloudability, so we had to go for another solution, the name of which I can't remember, to help us get the aforementioned functionality. There was an area related to some cost implications that we couldn't work on with Cloudability in my previous company. In general, I feel Cloudability wasn't able to support many resources.

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.

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.

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.

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.