We performed a comparison between CloudCheckr , SaltStack, and VMware Aria Operations based on real PeerSpot user reviews.
Find out what your peers are saying about VMware, Nutanix, IBM and others in Cloud Management."The recommendation section is pretty helpful."
"The solution is mostly stable."
"The most valuable feature of CloudCheckr CMx High Security is granular reporting. Additionally, the user interface is easy to use."
"The best feature I like about CloudCheckr CMx High Security is its simplicity. I love that it's not rocket science to use the solution. Even if you're not familiar with the cloud, you can easily figure out how to use CloudCheckr CMx High Security. You can use AWS, you can use Azure, and you can use GCP with the solution because the integration is quite simple. You can also use multi-cloud with it, and you could see the billing part. You'll have complete visibility into your cost which I love about the solution. I also love that data on any security issues and vulnerabilities are available on the go with CloudCheckr CMx High Security. You don't need to do anything different. Just run the scan and you'll have all these open findings in the tool, in terms of the priority level, so if it's critical, it will tell you, "It's critical," and you need to fix it right away."
"It will automatically suggest areas for optimization."
"The initial setup is straightforward."
"The solution is scalable for our purposes."
"It's one of the leading players for cloud optimization. It's hard to find anything better."
"SaltStack has given us the ability to deal with systems at scale and rectify issues at scale."
"The automation functionality has been most valuable. With a click of a button, we are able to automate provisioning, the build of new hardware and apply patches. These are all extremely important and differentiated tasks that can be automated in SaltStack."
"The product’s most valuable feature is its ability to provide environmental security."
"I want to build automation that is intelligent, part of the fabric of our environment, and is somewhat self-sustaining. I think SaltStack can help me do this."
"We monitor the configurations against CIS standards. We run CIS benchmarks and maintain configurations with higher CIS values for each server."
"The ability to programmatically describe the desired state of a single, or an entire fleet of servers, on-premises, and in a cloud environment."
"It is a highly stable solution."
"For me, it's the dashboard."
"It has helped us to reduce the amount of VM sprawl, VMs that are not necessarily used. We can then reclaim resources such as memory, CPU, and storage."
"The most valuable feature would be reporting because if frame or something is not syncing or we have an issue it will report us and give us a warning."
"It has allowed me to give the developers insight into what's actually happening underneath the covers. They used to only be able to see their app and now, they can see underneath. We've also given them access to see into the OS and we've given them a full stack view of how their application is performing."
"I'd like to see the streamlining of more wizards, more tasks that are canned. And it would also be good to see some more features around building the Blueprints, just to make it a little easier."
"It provides my team the awareness to see what's going on with the nodes and the clusters. It will then either rebalance them or allow the automation to rebalance them for us."
"The alerting feature would be the most valuable feature for us. It gathers more metrics. In the latest versions, there are metrics that are being exactly captured with vCenter which are a bit better. Aside for that it provides a historical analysis of metrics over time."
"The most valuable feature is how our metrics interact with each other. You can find what objects are needed and get all of the information about an object: How it works with the storage, CPUs, memory, and you can get an easy way to find the solution during troubleshooting."
"Many features still need to be implemented in this tool."
"The solution needs to work better with larger capacities of data."
"Self-healing could be a bit smoother and a bit cleaner, easier to access and more functional. That would help."
"The performance of the tool really needs to be improved."
"CloudCheckr CMx High Security is complex. There are a lot of menus, and if you do not know what you are looking for you can get lost. However, the interface is self-explanatory. It's easy to understand where to go to get what you want."
"The solution must improve its user interface."
"The reporting and analytic capabilities are very limited."
"What needs to be improved in CloudCheckr CMx High Security is integration. All the clouds are going quite fast, for example, all the cloud providers: Microsoft, Google, etc. CloudCheckr CMx High Security is good with AWS, no doubt about it, but with Azure and Google Cloud, I find that the solution is slow in that direction. If the vendor planned for CloudCheckr CMx High Security to be automated just for AWS, then it does make sense. If not, if the vendor is also targeting good integration with Google and Microsoft, then CloudCheckr CMx High Security integration needs improvement, in particular, it has to be faster. At the moment, its integration with Azure is not as good as its integration with AWS. With GCP, integration is nowhere."
"SaltStack's features are minimal."
"This solution could be integrated with more hardware for an improved offering."
"Its configuration process could be better."
"It is difficult to set up."
"There is a little bit of pain when it comes to libraries and what is needed to run the product."
"A hardened set of tests would be much appreciated."
"Web UI."
"I'd like to see more of the advanced reporting without having to go to the advanced product and paying the extra price. Canned reports are great, but you shouldn't have to pay for custom reports."
"We use a large installation of this solution with multiple nodes and so the setup was pretty complex."
"If you want to automate the resizing of machines, you should be able to schedule it, so it happens at two in the morning instead of right now, because if you do it in the middle of a workday that's a big no-no. Automation should be a bit more intuitive."
"When we first bought it, our vision was to use role-based access, give application teams access to view a dashboard for their stuff. We found out that the vROps tool can't handle more than about 20 concurrent sessions... We have some 3000 applications."
"If I put on the hat of a client, I would say cost needs improvement. For clients with reasonable-sized infrastructure farms, you're looking at licensing at either per socket or per VM, and if you have an installation of any size, you're doing it per socket, and the per-socket licensing is a little heavy. Per VM license, if they have large numbers of VM, it is just not practical."
"There are some problems with integration, particularly with Slack, though these have been improved in the latest release."
"A reporting engine would be good, where the database could dump into something like Splunk integration, so we could write our own reports."
"From a personal perspective, I would like it made clearer what options are available in the suite that the customer is not using."
