Amazon CloudWatch vs. PRTG Network Monitor

Cloud watch is great and essential if you decide to invest in AWS and have any need to monitor the health of all aspects of your VPC resources, or at the organizational level (multiple accounts). Another benefit of the service is constant upgrades at no additional costs; the software evolves to develop modules and interface improvements. For first-time users in AWS, this is going to take a bit to understand, so the learning curve to this metrics environment can seem overwhelming at first glance/use.

Incentivized

If there are a number of different protocols and devices to monitor PRTG is really an all in one solution. There are network specific solutions, telephony solutions, server solutions, etc - but this tool can do anything. Even if you don't use this tool as your main "monitoring solutions" every IT professional should have access to this tool for at least troubleshooting purposes. If you are looking for something specific built for a task you may be able to find [a] more direct and easy tool to use that would be easier and quicker to setup as customization is not needed.

Incentivized

• It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
• It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
• If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.

Incentivized

• Very, very configurable. You can create all kinds of monitors for all kinds of things. Plus it has loads of suggestions out of the box. It can get complicated but monitoring is complicated. Pretty decent interface and good support - active community.
• I really liked how easy it was to add alerts by SMS. So easy to setup.
• I like their sizing models (for purchase). We're actually small enough that we are free. But it's not free as in stripped down - it's free because we don't use many "sensors" and don't honestly have the need.

Incentivized

• Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
• Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
• By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.

Incentivized

• The probe service can be quite resource-intensive. This can cause false-positive readings from some sensors sometimes.
• The software gets updated very regularly. Whilst this is usually a good thing to fix bugs etc, it does meantime downtime of the monitoring quite often while they are installed.
• The ability to create Maps from Libraries. Very specific issue but a lot of people have been asking for it for years and it is still not available.

Incentivized

It is now an essential tool for monitoring and maintaining the health of our network and systems.

Incentivized

The tool is very intuitive to use and it is Windows-based (everybody knows how to use Windows) so it's easy to get into. Every time is setup in a hierarchy so if you have a good initial hierarchy design, it will really reduce administrative effort down the road.

Incentivized

Support is effective, and we were able to get any problems that we couldn't get solved through community discussion forums solved for us by the AWS support team. For example, we were assisted in one instance where we were not sure about the best metrics to use in order to optimize an auto-scaling group on EC2. The support team was able to look at our metrics and give a useful recommendation on which metrics to use.

Incentivized

I am giving this a 6 simply because I have never had to contact support. The online documentation is adequate for most things, and the user-maintained knowledgebase is excellent. The few times I have run into issues that were not easily resolvable with intuitive UI, I was able to find the answers that I needed either in the PRTG-provided documentation, the knowledgebase, or with a quick online web search.

Incentivized

I believe that CloudWatch is a better solution to use with AWS services and resources in terms of cost and ease of integration with AWS infrastructure services. But keep in mind that Elasticsearch is better at aggregating application-level metrics. We chose CloudWatch because of its capabilities to integrate and monitor AWS services in almost real-time.

Incentivized

I have deployed and tested three products for evaluation I found [PRTG Network Monitor] very easy to deploy, the deployment literally took not more than one hour including basic configuration and network discovery. After deployment few configuration changes and creation of maps, reports and little tweaking is required. [Then] it would go through its process of recommendation that took some time to complete, while [on] other hand other software's took lot of time to install and configure. And features were also missing, which resulted in decision in favor of [PRTG Network Monitor].

Incentivized

• We were able to set up log streaming, retention, and simple downtime alerts within a few hours, having no prior experience with CloudWatch, freeing up our engineers to focus on more important business goals.
• CloudWatch log groups have made it relatively easy to detect and diagnose issues in production by allowing us to aggregate logs across servers, correlate failures, isolate misbehaving servers, etc. Thanks to CloudWatch, we are generally able to identify, understand and mitigate most production fires within 10-15 minutes.
• Choosing CloudWatch to manage log aggregation has saved us quite a bit of time and money over the past year. Generally, 3rd-party log aggregation solutions tend to get quite expensive unless you self-host, in which case you typically need to spend a fair amount of time setting up, maintaining, and monitoring these services.

Incentivized

• The ability to analyze multiple pieces of information in one place, especially with historical data, has saved our IT department time and headaches. It would be so much more difficult to trace an issue without PRTG, just relying on event logs and an open task manager window.
• The cost is not cheap, so it's an expense that hits the bottom line like everything else. Figure in hardware costs as well, ideally a server outside of your main environment.
• I keep saying this, but the historical data piece is worth so much. There's really no good way to collect all of that information in one place without something like PRTG. And that definitely saves time and money in the long run.

Incentivized