Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
VMware SRM
Score 9.0 out of 10
N/A
VMware's Site Recovery Manager (VMware SRM) is a disaster recovery option, used to automate orchestration of failover and failback to minimize downtime and improve availability with VMware Site Recovery Manager.
N/A
Pricing
Amazon CloudWatch
VMware Site Recovery Manager
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
VMware SRM
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.
It's quite well suited for a medium to large size VMWare virtualization infrastructure where your production infrastructure can be failed over to a disaster recovery site. There are other cheaper options for a smaller budget business. Also, for a non mission critical virtual infrastructure, you can simply use VM backups such as Veeam backups for restoring failed VMs
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.
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.
It’s unfortunate, but more and more, the quality of VMware’s products and the technical support teams behind them has degraded significantly. We have opened several support requests within the last few months and ended up resolving a large majority ourselves due to the poor performance of their remote teams.
VMware is suffering from the same illness that’s affecting multiple U.S. technology firms, in that their focus has shifted completely away from their customers and moved to pleasing investors. In doing so, clients suffer because they do not get properly tested products and the support teams behind them are very weak and overwhelmed.
We worked close to a month trying to get SRM V6.5 to work. We have worked with many previous versions of SRM in the past while using HP EVAs, NetApps and Hitachi arrays, and we can honestly say that we are greatly disappointed with this release and the company.
We escalated right up to engineering, but their response times were brutally slow; the technicians were juniors at best.
As a technology leader, the last thing you want during a DR is to be dealing with a company that just can't deliver. SRM is not cheap, and you would expect much better products and support from VMware.
If you are comparing products, try other companies like Veeam... We ended up using them instead, the setup and execution was easy and seamless, and they answered all our questions quickly and efficiently. They actually do care about their clients.
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.
Sometimes we have to struggle explaining the problem and getting it resolved on priority. The overall quality of support team is not as good as it used to be in past.
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.
Entertained Veeam, however with SRM's tight integration and "brand" it was an easy decision. The cost for a 25 server license also weighed in the decision for using a VMware product. Plus I am a VMware fan and feel this option to go with SRM will transcend jobs.
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.
The biggest positive is that we have a data recovery solution that we can test and verify in a live condition. Prior to this we were only hoping we could recover from a disaster.
We've been only running for 4 months and haven't had to use SRM.
