What is our primary use case?
Nutanix Cloud Manager's biggest use case is compliance management, which includes configurations and drifts.
Cost estimation is another use case, but I don't know whether Prism moved that service because I've not used this product for cost estimation for the last eight to ten months. I've used other products for cloud health and other aspects.
How has it helped my organization?
The biggest generic benefit is the business value. There is no direct dollar benefit. The benefit is that the clients see MTTR reduction happening. They see low P1 or P2 calls or cases, but this decline happens over time. These are the benefits, but Nutanix Cloud Manager doesn't give you the benefits upfront. It's a journey because the system matures as you resolve low alerts. The outcome of this journey is the business value. For a small customer, it can take two months. For a mid-sized customer, it can take five to eight months. For a large enterprise, it can be twelve to eighteen months. There is no straight dollar productivity or dollar value benefit they will get. They cannot quantify those benefits. They can only say that their MTTR reduction happened, their system uptime is high, or their systems are more resilient.
In terms of the speed of the outcomes received using Nutanix Cloud Manager's low-code automation, I'm a supplier, I'm a GSI, and for me, the outcome is straightforward, which is a productivity improvement. The people who are doing day-to-day services don't need an automation engineer to automate their daily mundane tasks. With Nutanix Cloud Manager's low-code automation, I can just click and automate a task if the number of times an instance is repeated is high. It's a very simple left shift of the resources. An L1 engineer can do it for me, and I don't have to deploy highly skilled engineers. I can use their time to do more projects and provide value to the customer, so the low code in Nutanix Cloud Manager is always linked to the left shift of engineers.
What is most valuable?
The way we deliver it to our clients is that we don't tell them it's Nutanix Cloud Manager. We sell the functionality. If a customer wants to have end-to-end observability and AI ops built up for it, it's irrelevant to them whether I'm deploying NCA, or I'm deploying anything else. All that matters is the service, the functionality, and the cost for that functionality.
The most valuable feature is less or no implementation time. It should be up and running at any point in time so I don't spend time in transformation. I should spend more time in the operations cycle. The time to market is something that is very important. When it comes to operations, it should bring in the highest level of automation. I don't want teams to keep on troubleshooting in terms of whether it's a false alert or not.
I've seen that Nutanix Cloud Manager has fewer false alerts as compared to other products, such as SCCM.
What needs improvement?
Nowadays, we see systems breaking a lot. I know that the current features of Nutanix Cloud Manager help to monitor the container world and modern applications, but as more microservices are getting deployed, more micro-management of those services needs to be done. If NCL needs any improvement, it's in the microservices area because, over time, you will see more microservices getting deployed. Monitoring of those is an area that needs to be looked into.
For how long have I used the solution?
I know this product from the time when it was launched as Prism. I have been using Prism and Beam since 2015 or 2016. Being a System Integrator, I deployed it in a lot of customer environments.
What do I think about the stability of the solution?
It's a highly stable product, but it's yet to be proven for very big customers.
What do I think about the scalability of the solution?
It's good for up to mid-sized enterprises. For us, a mid-segment company has ten thousand virtual machines. They are running somewhere around 400 nodes of containers for elements. One of my big customers is running 6,600 Nutanix nodes.
Which solution did I use previously and why did I switch?
There were multiple solutions that were built, integrated, and deployed. All the incident correlations used to happen in BigPanda, SolarWinds, and ServiceNow, and the automation engine used to pick up those events and triggers and then automate them. They were there, but I required resources with multiple skill sets. With Nutanix Cloud Manager's low code solution, with a single click, an L1 engineer can do a task. My life is easy, and their life is easy. There is a productivity gain.
In terms of the comparison of Nutanix Cloud Manager with other solutions, as a supplier, every product is good for me. We just need to find the best and low-cost solution that delivers the functionality, even if that functionality is delivered by a small tool.
ServiceNow CMP is a comparable solution. It does the monitoring and other functionalities, but it does not look into the niche, modern technologies that are there right now, such as the containerized environment and multi-cloud container-native architecture. ServiceNow CMP needs another automation engine to deploy it because while it connects workflows to your end-to-end playbooks, it does not run them, whereas, with Nutanix Cloud Manager, I'm getting everything in a box.
How was the initial setup?
I'm a Chief Architect. Based on the customer's requirement, I do the big-picture stitching for the customer. Once our solutions team picks up the products, I can influence product usage. I'm currently handling database-as-a-service in the UK and Europe. I influence the selection of the products but not deployment.
What other advice do I have?
My advice would be to go for it without asking. As a mid-segment enterprise, you get everything in the box. You don't need to spend more money. You don't need to first spend money on VMware, then on SolarWinds, and then on your automation engine.
Prism is used a lot in terms of server and service monitoring, but it's not used for observability. It feeds into observability, but I'm trying to explore if it can be used for observability in a service model.
I'd rate it a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.