Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
N-able N-central
Score 7.2 out of 10
N/A
MSPs
and IT professionals use N-able™ N-central® to monitor and manage devices and complex
networks remotely. N-central provides
visibility and efficiency as the user's needs scale. N-central can help users:
1. Proactively monitor everything on a customer network—not just servers
and workstations—and troubleshoot.
2. Stay on top of threats with features like MFA, antivirus, integrated endpoint
detection and response, data backup, disk encryption, email protection,…
N/A
Pricing
Amazon CloudWatch
N-able N-central
Editions & Modules
Canaries
$0.0012
per canary run
Logs - Analyze (Logs Insights queries)
$0.005
per GB of data scanned
Over 1,000,000 Metrics
$0.02
per month
Contributor Insights - Matched Log Events
$0.02
per month per one million log events that match the rule
Logs - Store (Archival)
$0.03
per GB
Next 750,000 Metrics
$0.05
per month
Next 240,000 Metrics
$0.10
per month
Alarm - Standard Resolution (60 Sec)
$0.10
per month per alarm metric
First 10,000 Metrics
$0.30
per month
Alarm - High Resolution (10 Sec)
$0.30
per month per alarm metric
Alarm - Composite
$0.50
per month per alarm
Logs - Collect (Data Ingestion)
$0.50
per GB
Contributor Insights
$0.50
per month per rule
Events - Custom
$1.00
per million events
Events - Cross-account
$1.00
per million events
CloudWatch RUM
$1
per 100k events
Dashboard
$3.00
per month per dashboard
CloudWatch Evidently - Events
$5
per 1 million events
CloudWatch Evidently - Analysis Units
$7.50
per 1 million analysis units
No answers on this topic
Offerings
Pricing Offerings
Amazon CloudWatch
N-able N-central
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Amazon CloudWatch, there is no up-front commitment or minimum fee; you simply pay for what you use. You will be charged at the end of the month for your usage.
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.
In my opinion, N-able N-central is a good "learn your lesson and move onto something better" tool. I've used many RMM tools over the years and I feel that this one is slow, does a terrible job with reporting, alerting, monitoring, software deployments, etc. The ability to turn on services like AV, backup, etc easily is cute, but you're not going to be able to use your own tools with this easily. In my experience, if you do turn those tools on for testing during the trial, you'll be charged later (despite it being a trial). They also turn off your ability to monitor these increased costs or to turn them off yourself. As a company, I found that they were impossible to work with. The sales team is right there if you want to buy something - but if you need anything other than to buy something, in my experience, they take days or weeks to navigate. I found that they are not a terribly ethical company and are more concerned with making a few dollars than creating a partnerships with MSPs. I can see value is in the advertised price of $99 for a hundred endpoints. However, you need to remember to not trial any other tools (like AV, backup, etc).
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.
Remote tasks - entry-level techs can run basic tasks without physically touching a piece of equipment.
Remote support - remote controlling user devices is easy and saves a lot of time with having to initiate a remote session.
Management of devices, particularly patch management and anti-virus management - you can automatically approve and deploy patches and schedule automatic AV scans.
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.
Overall we have liked our solar winds experience, however, as our company has grown to support larger enterprises, this product does not have the functionality that our teams need in order to fully support them. The lack of granularity with backups and lack of ability to support nutanix environments is slowly drawing us into the use of other tools.
The user interface is fairly straight forward, with logic groupings for objects. I did not deploy this software, but am one of the daily administrators. Once you get the correct agent package (Which can be a challenge) the integration into AD is not bad. The UI could be more customized, but that may have been a design choice.
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.
Every time we have reached out to SolarWinds they are quick to respond, even offering support chat 24/7. Their support team is great and works with you to find solutions to issues. They have taken items we had issues with before and used those to create updates so that the issue is handled better in the future.
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.
Our version of SolarWinds was old and running on old hardware, but it was way easier to setup and do things with. It did not do everything N-able does such as patch management, or at least we didn't have a module to do so if one existed. However it definitely seemed easier to use and possibly more stable.
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.
