What users are saying about
195 Ratings
155 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.6 out of 100
195 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Attribute Ratings

  • Amazon CloudWatch is rated higher in 1 area: Support Rating
  • Elasticsearch is rated higher in 1 area: Likelihood to Recommend

Likelihood to Recommend

8.8

Amazon CloudWatch

88%
39 Ratings
9.1

Elasticsearch

91%
46 Ratings

Likelihood to Renew

Amazon CloudWatch

N/A
0 Ratings
10.0

Elasticsearch

100%
1 Rating

Usability

Amazon CloudWatch

N/A
0 Ratings
10.0

Elasticsearch

100%
1 Rating

Support Rating

8.1

Amazon CloudWatch

81%
14 Ratings
7.8

Elasticsearch

78%
18 Ratings

Implementation Rating

Amazon CloudWatch

N/A
0 Ratings
9.0

Elasticsearch

90%
2 Ratings

Likelihood to Recommend

Amazon AWS

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.
Read full review

Elastic

Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
Read full review

Pros

Amazon AWS

  • 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

Elastic

  • As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
  • Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
  • Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
Read full review

Cons

Amazon AWS

  • 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

Elastic

  • Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
  • Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
  • Schema changes require complete reindexing of an index
Read full review

Pricing Details

Amazon CloudWatch

Starting Price

$0.0,012 per canary run

Editions & Modules

Amazon CloudWatch editions and modules pricing
EditionModules
First 10,000 Metrics$0.301
Next 240,000 Metrics$0.102
Next 750,000 Metrics$0.053
Over 1,000,000 Metrics$0.024
Dashboard$3.005
Alarm - Standard Resolution (60 Sec)$0.106
Alarm - High Resolution (10 Sec)$0.307
Alarm - Composite$0.508
Logs - Collect (Data Ingestion)$0.509
Logs - Store (Archival)$0.0310
Logs - Analyze (Logs Insights queries)$0.00511
Events - Custom$1.0012
Events - Cross-account$1.0013
Contributor Insights$0.5014
Contributor Insights - Matched Log Events$0.0215
Canaries$0.001216
CloudWatch Evidently - Events$517
CloudWatch Evidently - Analysis Units$7.5018
CloudWatch RUM$119

Footnotes

  1. per month
  2. per month
  3. per month
  4. per month
  5. per month per dashboard
  6. per month per alarm metric
  7. per month per alarm metric
  8. per month per alarm
  9. per GB
  10. per GB
  11. per GB of data scanned
  12. per million events
  13. per million events
  14. per month per rule
  15. per month per one million log events that match the rule
  16. per canary run
  17. per 1 million events
  18. per 1 million analysis units
  19. per 100k events

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up 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.

Elasticsearch

Starting Price

$0

Editions & Modules

Elasticsearch editions and modules pricing
EditionModules
Standard$16.001
Gold$19.002
Platinum$22.003
EnterpriseContact Sales4

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up fee?

No setup fee

Additional Details

Likelihood to Renew

Amazon AWS

No answers on this topic

Elastic

We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Read full review

Usability

Amazon AWS

No answers on this topic

Elastic

To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
Read full review

Support Rating

Amazon AWS

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.
Read full review

Elastic

We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Read full review

Implementation Rating

Amazon AWS

No answers on this topic

Elastic

Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Read full review

Alternatives Considered

Amazon AWS

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.
Read full review

Elastic

As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
Read full review

Return on Investment

Amazon AWS

  • 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

Elastic

  • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
  • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
  • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
Read full review

Screenshots

Add comparison