Likelihood to Recommend
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.
Elasticsearch is really well suited for searching text (Natural Language Processing) and you can fine tune the searches and scoring very well. I like the ability to find Significant Terms in the Index, where you can find aggregations that are really relevant to a specific search. It also allows for queries to lead to new queries via aggregations which is great for navigating your data. It is less suited to doing more complex aggregations where slices of data are required to be processing using guassian normalizations. And doing searches which join different documents is very very hard, and requires serious thought on how to denormalize data.
- 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.
- 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.
Engineer in EngineeringInternet Company, 201-500 employees
- 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.
Professional in Finance and AccountingFinancial Services Company, 501-1000 employees
- Elasticsearch is highly distributed, but it takes time to tune so you get the right performance out of your cluster.
- The query language is not SQL, so it's not a straightforward conversion from an RDBMS to Elasticsearch for searching through data.
- There are lots of ways to insert data into Elasticsearch, and some are better than others (batch vs. single insert). Need to experiment with your own data and environment.
Likelihood to Renew
No answers yet
No answers on this topic
Based on 1 answer
We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Amazon CloudWatch 7.0
Based on 2 answers
The tool collects a great deal of data, and data that's not available many other places. But the data is hidden in obscure places, and the logs are hard to read and follow. The user interface could use a heavy rework, and several companies have made a business out of scraping the data and presenting it better.
Professional in Information TechnologyHuman Resources Company, 51-200 employees
Based on 1 answer
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.
Vice-President in Information TechnologyComputer Software Company, 1-10 employees
Amazon CloudWatch 7.9
Based on 16 answers
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.
Based on 12 answers
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.
Consultant in Information TechnologyInformation Technology & Services Company, 201-500 employees
No answers yet
No answers on this topic
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Contributor in Information TechnologyPharmaceuticals Company, 51-200 employees
Amazon CloudWatch is efficient, reliable and has a high speed response as compared to its competitors and it maximizes an application's life at the same time giving you the best load balance and storage, the services that Amazon CloudWatch provides are way better and cheaper for the prices attached to them.
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.
Engineer in EngineeringHealth, Wellness and Fitness Company, 1-10 employees
Return on Investment
- 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.
- When we where initially exploring logging solutions, Splunk was the only vendor in town and they where extremely expensive ($60,000). We haven't revisited them since as ElasticSearch has accomplished all of our needs.
- We haven't spent anything but Admin hours to maintain our ElasticSearch cluster. Right now we haven't incurred any cost of ownership as I have been maintaining the cluster myself.
- We have a huge project to grow a new part of our business, but I am not sure if I can spend the time to really update cluster to support the new Logstash features & any syntax changes so I am reluctant to do so. Time is increasingly becoming scarce, so catering to the latest and greatest features that offer little to our organization isn't something we are interested in pursuing though we are going to need to update the ElasticStack eventually.
- Since all of our metrics are in ElasticSearch, we have had nice trove of data to build our apps around, apps that require specific metrics. Prior to ElasticSearch, we had to build our own tools that handled that metric collection. The cost savings here is that we maintain a simple script that reports back information in our reporting interface vs rolling our own database metric solution that must be modified for every app we develop. That has equated to a huge saving in developer hours in our organization.
Premium Consulting/Integration Services
Entry-level set up fee?
Amazon CloudWatch Editions & Modules
|First 10,000 Metrics||$0.301|
|Next 240,000 Metrics||$0.101|
|Next 750,000 Metrics||$0.051|
|Over 1,000,000 Metrics||$0.021|
- Per Metric
Additional Pricing DetailsWith 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.
Premium Consulting/Integration Services—
Entry-level set up fee?
Elasticsearch Editions & Modules
- per month