Amazon CloudWatch vs N-able N-central

• 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.

Read full review

• 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.

Read full review

• 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.

Read full review

• Expensive software
• The support team are terrible
• Sales team will promise the world to get you over the line
• Subscription management is tedious
• Old software with very little development and the support team will not provide any further information on this - no roadmap
• Integrations galore - but none of them are effective

Read full review

• 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.

Read full review

• Reduced time to manage and support servers and endpoints.
• Provides support dept with more accurate information to assess and resolve issues quicker and more efficiently.
• The subscription cost associated with N-central, to our clients has a good profit margin for us.

Read full review