Try to find at least two use cases for the product and continue validating it after the installation.

I'd rate it a solid nine out of ten.

I give the solution a nine out of ten.

I definitely recommend the solution, as it was my first time using it and I really felt it captured all the necessary elements of the environment. The main benefit is that vRealize Network Insight captures micro-segmentation, which is one of the best products from VMware. The solution helps micro-segmentation achieve its purpose.

When comparing vRealize Network Insight to other solutions such as SolarWinds and other monitoring tools, vRealize Network Insight is more user-friendly.

I rate the solution ten out of ten.

For our requirements, five people are needed to maintain the solution. I recommend the solution tool for all networks and security.

The product is highly regarded, and many customers have been using it along with other VMware products like vSphere and VMware vCloud Usage Insight. However, recently, there's been a trend among customers, especially those using VMware for a considerable period, to explore the potential of migrating to the public cloud. The common concern among these customers is how the VMware products will perform in the public cloud environment.

Migrating instances from VMware to different platforms is not easy, especially when dealing with many instances across multiple customers. Customers are keen to maintain the functionality of their existing VMware products but prefer to run them on the public cloud instead of on-premise servers.

Our clients for vRealize Network Insight are enterprise businesses. I rate it a nine out of ten. 

If you are having too many issues with your network, having issues with tracing the flow of your network, this is the product you should be using to troubleshoot the issues.

I rate it a nine out of ten. It's not a ten because of the compatibility issue.

Use the product. It's pretty cool.

We need other metrics that could be useful for monitoring purposes. So, we need a solution with parameters and metrics. Overall, I rate the solution a nine out of ten.

We are a VMware business partner in Turkey.

I'd rate the solution eight out of ten. 

There is not an easier way to do this. If you have unlimited time, maybe go look at something else. But if you don't, then this is would be the way to do it.

I rate it a nine out of 10. It's a fantastic product, it's great. Some of the things I think it should be able to search on, it doesn't. I would also like to see tighter integration with some logging and SNMP-type information. I also use Splunk so I'd like to see something with Splunk. I know it can do vRealize Log Insight but that doesn't seem to do a whole lot for me yet. I only gave it a nine because I know there's so much more potential there. I would tell anybody "Get it". I rated it very highly but there's a lot more potential and room to grow.

Overall, I would give vRealize Network Insight a nine out of ten. 

I want to say it's a 10 out of 10. If they fix that micro-segmentation thing it will absolutely be a 10. Right now it's about an eight out of 10. I think it's just a big jump. If they can fix that micro-seg, that means so much more to me, so I would give it that extra boost for that. But the usability of it, how nice the interface is, those are great. If they improve the API that might get us to a nine, but if they get the micro-seg, I'll give them the other two points.

The way technology works, you've got to catch up. If you're basically staying in a legacy environment, and everything is moving rapidly, you've got to stay ahead of the game.

Most important criteria when selecting a vendor: customer support.

My recommendation: If you're looking to minimize your downtime, your troubleshooting, and the amount of resources being used in order to look at logs and troubleshoot an issue, this is the solution.

I love what we can do with this and I love everything it gives to us.

I rate it a nine out of ten because I don't see users complaining a lot. For what we need, for the most part, we get it. It's not 100 percent, it's not like something we distributed to the whole organization. But I'm sure the CIO will want to do that when we can. 

I would rate this product an eight out of 10. I might give it a higher rating if we used it more. We used it for a period of time and then we stopped using it. There was nothing wrong with it, we just didn't use it enough to see it as a 10 out of 10.

The most important criterion when selecting a vendor is finding one who will actually give what is promised.

I rate it a nine out of ten. I'm a little bit skeptical, I never give a ten. But otherwise, in the next release, if they made it more intuitive - it's definitely intuitive - but if there were some more features and it let us know about east-west traffic as well, that would be more helpful.

If you're VMware shop, investigate this deeply because it makes sense to live in the ecosystem.

It's a pretty good system if you're doing troubleshooting and microsegmentation. As a troubleshooting tool, it's a level-3 troubleshooting-skills tool and it's very easy to use and very easy to find the information that you need.

I rate it a seven out of ten, only because it doesn't have all the vendors - at least the switch vendors - in there. They only have Cisco, for the most part, and you really need all of them to make it because companies don't just use Cisco for everything.

Support is very important, to be available especially for issues that may be new with the features which we're trying to implement. We tend to request support quite a bit, so support is definitely very important.

I would definitely advise, especially healthcare companies that need to secure their products, NSX using vRNI as their tool. To implement it, I would highly recommend that they invest the time to learn how to use vRNI.

If you have a VMware suite and you are going to use NSX, then I would definitely recommend vRNI.

I rate the solution at eight out of ten. I'm still getting familiar with it. The UI, even though once you get to know it, it's easier, still it's hard to figure out by yourself. You have to go read, watch videos. It has a lot of data on it. So that is an issue.

We would absolutely recommend it. In fact, we've had that experience where it was recommended to us and we said, "We need this, we need to do this."

We are very positive so far with everything we've seen in this tool.

I would rate it an eight out of 10. It's not a 10 because of our experience with the vendor. I believe the product is a great product and, obviously, the VMware applications that we're using, we have had no issues with them.

I would rate the vRNI a ten out of ten. It has given us value since day one. We can see more than before. This helps.

For the most part, it is user-friendly. It continues to grow and mature. It's definitely headed in the right direction. The fact that they continue to want to improve the customer experience is important. The product is great to begin with but they realize that nothing is perfect and they want to keep improving it.

We typically just deploy the latest version that we have, and that's it. We don't go back and do upgrades. Either the customers are doing that themselves or we don't have a specific service that does that. 

This is a must have product if you're a very big gamma customer. You have to have a way to analyze how networking is slowing through your environment.

We used to have the 1000V when we had Cisco for our Cisco customers, and we could use some of that solution, but there is not really any other tool that will provide the type of fidelity and richness of beta that you will need from your VMware environment regardless of whether you're deploying NSX or not, giving you that rich visualization of what's happening in the network layer and what's happening with the application layer within that networking layer in VMware. This is the only tool that you can obtain this level of richness from it.

Most important criteria when selecting a vendor is that they're there when you need them.

For someone looking at this solution: Look deep.

I would recommend the product. I don't think there is any other product like this on the market right now.

I rate this product at seven out of ten because the product is great but there are still a few more improvements that can be made to it, as I said above. It could have more physical devices integrated and supported.

When selecting any type of vendor, our most important criteria is support.

Make sure the solution you're looking at is compatible with what you want to do and that it has future growth to it; not just a pinpoint solution but a solution that is part of a bigger vision. You don't want to buy a product that does just this one thing and then you have to buy another product to do something else. Make sure it has interoperability and integration points with some of your bigger infrastructure.

I would rate vRNI at eight out of 10. It would be a 10 if it could bubble up deeper application and user information.

It's a great solution.

You do need knowledge and understanding of network traffic, protocols, and ports to understand when you do a search, since you receive flowcharts about the ports in use. This is more technical knowledge of how your network works. However, the tool is very much intuitive.

The rating for the product would be a nine because I don't know of anything that would be a ten. Nothing's perfect.

The most important criterion when selecting a vendor is whether or not we think they're going to survive for more than the next license cycle.

I would rate this solution a strong nine out of 10. It would be a 10 if it were free.

If they have VMware, and they're gonna stick with it, then this is probably the tool they want to look at for their network flow.

Just know what your network is and what you intend to do in terms of segmentation. Know your network, know your environment.

We just started with it recently. We are still working on it, to get familiar with the product.

The first criterion, when selecting a vendor, should be technical support. Whenever we call, we should get technical support. Support is the main thing.

It's definitely worth investigating. You need to look at the environment, but it's worth the time to look into it and see if it fits with your purposes.

I would tell a colleague who is looking into this or a similar solution that vRNI is a great tool because, without it, it would be impossible to manage the operations part.

I rate vRNI at eight out of ten. For the other two points, I would need more regarding the microsegmentation part. It doesn't give me the clarity I want. It captures a lot, but it doesn't give complete clarity. That is something I am looking for.

When looking for a vendor, support is the main criteria.

It's easy enough to try. Get with their account team, get some trial licenses and give it a whirl. It's worth spending a weekend to give it a shot.

It's hard for me to give it a 10 out of 10, it's hard for me to give it a six out of 10, so my rating is in the middle. The only reason I would not give it a nine or a 10 is for cost reasons. It seems to be one of those things that really belongs as part of the product inherently and not as an add-on. That would be my only concern.

We are a reseller of VMware. We're known as a principal partner and we have the highest level of partnership agreement an organization can have with VMware.

Our organization is quite a large organization that deals, and we have many various different business units concentrating on specific enterprise applications.

In terms of advice I would give to other companies, my personal opinion is that they shouldn't waste time, especially if they know what they want, and start moving towards a cloud consumption-based environment. Network insight is critical. Without that, you're going to introduce additional latencies and problems into your environment that you don't want. So, as a first step to your cloud journey, you have to have a good view of your network environment - especially with your applications and how they are talking to all the other applications. It is critical. I think it's a must-have.

I'd rate the solution eight and a half out of ten.

I would definitely endorse the solution.

There's no real advice. You'll know if you need something like this or not. You don't just purchase it and then hope for the best. You have a use case for it.

If you are going to implement NSX, it's a great tool. It really helps. The network piece, they should look at that, and see what to do with NSX.

Most important criteria when selecting a vendor: good support.

Do the training before purchasing. Research the product and its competitors.

Most important criteria when selecting a vendor: technical knowledge. They need to understand their product.

The most important criteria for selecting a vendor: Functionality of the product, it's got to work, then responsiveness of the support.

Make sure you check out the demo, make sure you have enough time to check out the demo, run it in your environment for a while, and study up as much as you can on it.