The initial setup is straightforward. It took us three days to set up.

The setup was challenging initially because we were not familiar with the solution. Now that we have experience, everything is easy. 

The setup is easy. The solution is cloud native so there is no deployment. You just configure the solution in Azure and it is ready to go. 

Configuration can take one to five days depending on the complexity of your environment. 

The initial setup is straightforward.

The initial setup of Azure Monitor is easy. The deployment took a day or two because it is available by default. It is really an out-of-the-box solution.

The solution is straightforward and very simple. It's not complex at all. We're effortlessly engaging with it. We implemented ten applications in one week.

Only two people are needed for deployment and maintenance. They are admins. 

I faced many issues in my previous organization since I was a beginner in Azure, but I have no issues now. When implementing Citrix on-premises to Azure, we had some problems with adding sensors and SSL certificates.

The deployment duration depends on the use case. It depends on what you want. You don't deploy Azure Monitor itself. It's not like other tools where you have to install nodes and install the software and deploy it. It comes natively with Azure as a platform, so the implementation time is just dependent on what the client wants out of it. For our use case, we set up a template of about 15 to 20 key metrics that we monitor, which probably doesn't take longer than a day to deploy. It's all templated. We just run a bunch of CLI commands, and it deploys those templates, but if you have a customer who wants to start monitoring more intricate or complex things such as SQL databases and applications, you can probably spend months on it.

In terms of the number of people required, one person can do it if he or she has the skills for it.

The initial setup is straightforward.

We find the initial setup to be straightforward as we have extensive experience in it. However, configuring Azure Monitor may prove to be complex for those who are less experienced. The deployment takes about 30 minutes. The deployment process is using a CICD workflow that is fully automated.

The initial setup of Azure Monitor is straightforward. The process took us approximately one hour.

The setup for Azure Monitor itself is easy to understand and, for generating logs and such, it's a simple process of configuring how you would like to gather your logs and for how long you would like to keep those records, etc.

It won't take anyone that much time to deploy their monitoring system with Azure Monitor. This is especially true if you understand your business needs well, because you can then quickly integrate Azure Monitor (and Log Analytics or Workbooks) inside your application as appropriate. As an estimate, it could take up to three or four hours at most.

The initial setup is easy. Those who opt for Azure Monitor should use it as per needs. For example, one can use it to monitor resources, administrative operations, or log events. The solution was deployed on the cloud.

A part of the setup process was straightforward. At the same time, a part of the process required some guidance because the Azure monitor evolves constantly. Most of the time, the blog post or guidance article on how to set up gets outdated quickly. Sometimes many things don't work as expected or as written in the Microsoft documentation.

The initial setup was straightforward, and deployment took around thirty minutes. I would rate the process nine out of ten.

The solution is very straightforward. It's very easy to implement. 

We can use different services by Azure, such as virtual machines or Web Apps. These are all quite frequently deployed and it's not difficult. 

There needs to be a better process or method to deploy and configure it. Currently, there's a lot of manual intervention. It is not really an out-of-the-box solution.

If you want to get help, you will have to pay for it. Otherwise, you just do it on your own. The problem with doing it on your own is that if you're not so familiar with it, then you have to first familiarize yourself with Azure and setting up different alerts, etc. You really don't get a whole lot of these complexities with Dynatrace.

The initial setup was straightforward and not complex. Deployment took a couple of days, and it was deployed in-house.

The initial setup of Azure Monitor was in the middle range of difficulty.

I found the initial setup process to be straightforward. 

I'd rate the ease of deployment ten out of ten. The deployment itself was fast and took maybe ten to 15 minutes. 

Just two people were involved in the deployment process. They were regular architects or technical individuals who were part of the deployment.

ONce deployed, the solution itself does not require maintenance. 

The initial setup for Azure Monitor is quite complex. If I would rate its setup from one to five, with one being complex and five being straightforward, I would rate it 1.5.

With Azure, implementation needs to be carried out in multiple places and you need to add other things to get the information and that's a tedious process. The Dynatrace setup is much easier. 

The solution's initial setup was straightforward.

It was pretty straightforward. 

I am experienced with Azure, and hence, the installation was easy. However, an inexperienced person may find it difficult. 

The initial setup was very straightforward. Transfer to the solution required some training so I think in total it took us about two weeks. 

The initial setup is relatively easy. It requires time and involves a lot of work.

It depends of the things that you're going to monitor. For example, when configuring a third-party social Internet application on IaaS services and PaaS, I don't have a software development background. Therefore, it's quite difficult to ask the infrastructure guys, "What is something that I need to monitor from the Azure's SQL Server databases and infrastructure."

It's a fast service to deploy. It's more about defining the configuration. You need to find the right attributes to monitor. It takes about two weeks (10 to 20 days) to assign what to monitor. The actual configuration is quite fast. 

The deployment of the solution is somewhat complex because not all the tools are easy to understand. Just like New Relic, you use the SQL language to do the requests that you want to have specific for your APM. That's a little bit different than I'm used to. I'm trying to learn the language right now.

From what I've seen so far, for our use case, it's a bit complicated if we have to monitor directly from the virtual machine or if we need to pull logs and stuff from the virtual machine to create an API and all that. You need a developer to be able to create an API for you so that the Azure Monitor can consume or pull the logs. From the discussions I've had with the cloud engineer and what we've seen, that area is a bit complicated. That said, it's not like it can't be done.

As this is a cloud solution, the initial setup was very easy. Deployment took only 10-15 minutes — it's very simple. 

The initial setup is pretty straightforward. We deployed in stages over about a month.

The initial setup was not that complex but it was definitely not straightforward. You need to have certain design planning in place. We are integrators, so we have an internal team who was responsible for it.

The duration of deployment depends on the size and the number of servers that you need to monitor. Sometimes it takes 20 or 30 days, sometimes takes five days or even less. So it depends on the client size and how much he or she wants to evolve and develop. 

I would say that one person is enough to do the deployment; it really depends on the kind of business.

The initial setup is not complex and is, in fact, quite straightforward. It's good.

I didn't participate in implementing the solution, so I can't personally evaluate how the process went. I'm not sure if it's complex or straightforward. However, one of my technicians handles the process, and it's my understanding that it's very complicated to set up.

The product is in the portal, so you don't really need to set it up. When you get your subscription it is all built-in. If you're setting up customized resources and alerting, then you need to set up the action groups and some other things. For example, I put automation on group creation which sets the alerts and additional parameters. It isn't necessary but it is a good option to take advantage of. The only thing that gets in the way during setup is the integration. I think the setup is getting better and easier than it was.

I would say that the initial setup is somewhere between easy and complex. It starts a little bit easier with the wizards, but if you want to achieve the best performance then you have to know the product well.