The setup for this solution is pretty simple and anyone can do it if they are on AWS. Setting up all our VPC and private links connecting to our gateways took some time, but CloudWatch setup was a no-brainer and took a couple of days. 

The initial setup of Amazon CloudWatch is easy.

The solution is deployed on the cloud.

The initial setup for Amazon CloudWatch was quite okay, particularly for the standard alarms provided by Amazon. Still, for the custom alarms, such as memory and disk alarms, you have to put in some effort because if you make changes to the system, you'd also have to make changes in the scripts as well, so if that could be automated, it would be beneficial.

The product's installation phase is very easy. In our company, we didn't face any problems with the product's installation part.

With Amazon CloudWatch, the time taken for the installation phase is only related to the configuration part. You just need to do the configuration on the basis of availability, after which you need to make sure that you have a configuration ready, making it a very easy process that doesn't take hours to finish.

The initial setup was not complex.

It is hard to configure; it is not a straightforward tool.

The initial setup is pretty straightforward and simple. It's easy. It's not overly complex. 

The usage in both CloudWatch and Datadog is about the volume. People simply have to be mindful of how much they want and how they want to index and manage them. Otherwise, it's pretty straightforward.

One doesn't have to do any setup for CloudWatch logs. Only CloudWatch Alarms need setting up. Whenever you create a Lambda function, it automatically logs to CloudWatch.

The initial setup is easy. The deployment takes around five minutes. It is very fast.

The solution’s initial setup is easy.

The initial setup has medium complexity. You have to know what you're looking for.

The setup is very straightforward and took less than thirty minutes to install.

The initial setup of Amazon CloudWatch is simple. The deployment of the solution only took minutes.

I rate the initial setup of Amazon CloudWatch a nine out of ten.

This solution is easy to set up. It's not complex. You just need to run the Amazon CloudWatch agent in all the services. Once we install the agent into our services, we'll be able to fetch the log regularly.

The solution was easy to deploy.

It's very easy to implement. It's simple. These are solutions that are very simple to use, and therefore, there isn’t really any complexity involved.

You may not need so much technical knowledge or information to use this product. That said, there are some policies where you would need to know how to write the script. Still, it would be simple for anyone to use quickly.

The initial setup for Amazon CloudWatch was easy. It wasn't difficult. It was easy for my team to develop a microservices web application, but it would still depend on your experience and the way you use the solution. Whatever my team did was completed within one day.

The initial setup of Amazon CloudWatch is simple. Everyone can do it if they learn how to do it.

The product's setup is easy. The tool's deployment depends on scenarios like the metrics, events we create, etc. 

The solution's initial setup was fairly simple and straightforward. 

The deployment took less than a week. Once we started, our first task was to understand the solution and how we could best leverage it for our environment. Once we had that configured, we then started working towards deploying it.

The initial setup is easy. 

I rate AWS CloudWatch nine out of 10 for ease of setup. Deployment is practically instant. 

We have the complete documentation to set up AWS. We use Confluence for our documents. The steps to set up AWS are clearly mentioned in the documentation.

There is no setup for Amazon CloudWatch. It is on the cloud and all that is required is a migration.

The solution is very simple to set up. It's not overly difficult or complex. It's also easy to configure. 

How long it takes to deploy depends. CloudWatch is just a click away, however, integrating other services into CloudWatch, takes time and it all depends on what kind of complex scenarios you need to monitor. It's an iterative thing. For example, when we pinup other parameters that we are going to monitor on CloudWatch, it all takes different time limits and it takes a little bit of learning of the specific application. We cannot actually tell, on the implementation level, how long it will take. We cannot give a specific time range. However, activating CloudWatch is a few minutes and just a few clicks. 

You don't need additional staff for configuration, you would need only one. Of course, it all depends on their specialty. For example, if a person who's doing a program would like to integrate into CloudWatch, that specific specialized person would know what needs to be done. The DBA would want to send some monitoring parameters into CloudWatch, so that person would do that part of it. CloudWatch is segregated into different roles. It's not the same person most of the time who does all the configuration. 

The initial setup was quite easy.

The initial setup was a bit complex because we were new to AWS. 

It took us time to integrate EHNs because we had difficulty discovering traffic and TCP connections. 

The KPIs that needed to be monitored were books of medium to high complexity. 

As we became more proficient, we progressed quickly but that always depends on the complexity of the stack. 

For example, Java is easy but .Net is complex because many services are not API exposed so they have their own DLS running on machines. 

Its setup is easy. AWS documentation is there, and you can find a lot of guidance on it. You can configure it easily.

The initial setup process is easy.

The initial setup was easy.

The setup is straightforward for what it is. It's a little of both. It's honestly like any technology, it's a little of both. It can be very straightforward, depending on the size of the client and what they currently have. If it's a very large enterprise client, it's going to be much more complex. If the size of their instance is running a hundred applications, versus a small company that may only be running 10. It's just going to be much more complex, making sure that everything is connected, running and that it's watching everything correctly. The setup becomes a little trickier.

The initial setup was straightforward. We didn't face any complexities.

Amazon CloudWatch's initial setup is easy.

The initial setup is straightforward.