The initial setup for vRealize Log Insight is straightforward, but you'd still have to make a few decisions about whether you want to deploy the solution on a single data center or multiple data centers, so you need to have an understanding before deploying vRealize Log Insight. Once you've decided with a clear rationale behind it, it's a very straightforward deployment.

The solution was deployed four years ago, and from the due diligence phase to its actual design implementation, it took approximately one week to deploy. Integrations for vRealize Log Insight took another week, but predominantly, the due diligence, design, and implementation of the solution took two weeks, then integrating and authenticating it took another week, so the deployment took three weeks overall.

I've done capitalized operations, but in the beginning, when we started the VMware deployments, it took me a day to complete because it was not a deployment on a local area network, a flat network, but it was a deployment in a DMZ. 

So, one had to ensure that the rules are in place for port forwarding and such. It was not an easy deployment, but it took me a day to complete everything, including securing the storage.

We use it on a private cloud, on-premises. The private cloud is a VMware internal product. We're not integrated with an external cloud, but we do have Azure and AWS in another team. They run in their own space. 

So, our setup is a pure native VMware internal cloud.

We handle our own maintenance. For major upgrades, we schedule a call in advance with the vendor in case we bump into issues. We perform our own upgrades across our environment, following VMware's recommendations.

The product's deployment phase is easy.

The solution can be deployed in a day or two.

One architect and one engineer can manage the product's deployment phase.

The solution is deployed on the cloud and on an on-premises model.

It is definitely easy to deploy. It is relatively simple if you are very familiar with the VMware environment, specifically the vSphere environment, if you have configured vCenter, ESXi, and other VMware. 

You will have to deal with some obvious issues, you will have to deploy it, and you will have to decide how many components to monitor. 

You will have to know what exactly is the size of your environment, how many virtual machines you will be running, and how many vCenter instances are you running in your environment. 

It is pretty simple because you don't have to configure or click, click, click those things.

It has the ability to automatically add to the services. As a VMware person, I am used to configuring everything VMware. In my opinion, it is easy.

It's easy, I would rate it a four or five out of five.

When you have a cluster environment, or, a multi-site environment, or a few locations in different zones, you must deploy the same. You have to put this in a cluster now.

When one of your nodes is located in Sydney, while another is located in Amsterdam or something along these lines. In cluster mode, you must comprehend the mechanism. I am referring to how the cluster works.

A load balancer must be installed on top, and the load balancer will determine where the traffic goes.

It would be difficult in cluster mode.

It will be difficult for those who do not understand the cluster terminology. However, in a single-site environment, it is straightforward in my opinion.

I would rate the initial setup as eight out of ten, so relatively straightforward.

The initial setup was easy because it was a pre-integrated system. It was a quick deployment. We did not have a lot of challenges. The deployment took three days to deploy.

The initial setup was straightforward. The solution was deployed quickly, but we are very specific in our case as we use Boolean Block Infrastructure based on VTS/VCF. Also, the VTS/VCF comes with their live suite, so there is a VN and a second manager for the solution we manage.

Setting up Log Insight is easy. The deployment time depends on whether you have a single node or a cluster. 

The initial setup took weeks.

The product's implementation phase is easy.

The initial setup was quite straightforward. The installation itself is simple. You'll need some time to generate more insightful reports over a period, but nothing unusual. It was quick and easy. The entire deployment took a couple of days.

In our case, the entire ecosystem is completely VMware, so it's very native. We start with ESXi, then vCenter on top of it. Then comes vROPs or vRealize Operations with vRealize Automation (vRA) in between for provisioning automation and orchestration. 

vRA with vROPs helps us provision VMs quickly. vROPs also help get storage from different, non-VMware sources, further improving our provisioning operations. 

Then vROPs or Aria does real-time monitoring and tracks resource usage to ensure efficient compute resource allocation. You don't waste resources; you have them where you need them.

The initial setup was easy.

The setup and installations are very, very easy and straightforward. There is nothing that takes much effort and in that way it is fine. 

The amount of time that it takes to do the installation depends on how big your infrastructure is. If we are going to do a single node, it may take a few minutes. If you are going to do an installation for a cluster using Log Insight, then it might take some additional time, but it based on the number of modes. It total, it may take an average of twelve hours. 

The initial setup was straightforward and I did not have any challenges.

LogInsight is user-friendly and straightforward. I rate it 8.5 out of 10 for ease of setup. After deployment, maintenance isn't a challenge so long as you keep it updated. You may need to update the software to stay in line with the upgrade roadmap, but the rest is fine.

The initial setup of the solution, as far as I can recall, was straightforward. There wasn't much complexity involved.

The solution's initial setup is both straightforward and complex. It depends on the environment. Working with the solution is simple, but in our current use case, we have some difficult configurations that add complexity to the process. You need two people to maintain the solution once it's set up.

The initial setup was okay, but it wasn't exactly straightforward. For the implementation, there was a problem with the VDI solution. For example, with the Horizon 7 version, we had some problems setting it up. We had to do some studying up on the solution and did a lot of Googling to find the answers we needed. We were able to resolve it in the end.

The initial setup was very straightforward. It's difficult to measure deployment time, it really depends on what you're doing. If it's a single VM deployment it shouldn't take more than an hour.

The initial setup is straightforward, but you will need a technical person to understand how it works.

The initial setup is very straightforward. Deployment took a couple of days.

It was very easy to setup. I didn't have any problem with that. Log Insight is simple to install and connect to the environment, but the problem arises when you want to look for some information. This is a large problem because the documentation and examples on the internet don't give us so as much information as we need.

The initial setup had a moderate amount of difficulty, although it was mostly straightforward.