Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Aternity
Score 5.1 out of 10
N/A
The Aternity Digital Experience Management platform provides AI-powered analytics and self-healing control in order to improve employee productivity and customer satisfaction, get to market fast with high quality apps, drive down the cost of IT operations, and mitigate the risk of IT transformation. Formerly from Riverbed Technologies, Aternity became an independent company in 2020, and assumes the the APM capabilities of the SteelCentral AppInternals solution, formerly from Riverbed.
N/A
Pricing
Amazon CloudWatch
Aternity Digital Experience Management
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
Aternity
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.
We are a services organization and we use Riverbed SteelCentral AppInternals with our customers. It has allowed us to expand the footprint in the application management business with virtually all of our major accounts. We were able to expand and go into other applications that we weren't in or offering previously. Now, we have a new value proposition for our customer enhanced visibility, enhanced stability, and we can reduce our cost to them because our cost structure is reduced by using Riverbed SteelCentral AppInternals.
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.
The tool demands High CPU resources to perform monitoring which reduces the overall performance and the user experience is sluggish
Also a good amount of training is required to set up the different use cases and monitoring parameters which in return demands a dedicated resource to work on the tool
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.
The support I give the highest rating because it is really amazing. Every time we triggered the tool support, we were very well served very quickly and efficiently. The problems were solved quickly and without stress. The staff helped us within minutes and had a lot of patience with us
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.
There is a wide variety of APM solutions out there for companies to pick from. Riverbed AppInternals sits near the top of the stack certainly. We already deploy steelhead units across the estate with client licenses, that aided us in our decision to select AppInternals. We found the costs of AppDynamics and New Relic ( which we had trials for) both costly against AppInternals.
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.
This product has really wonderful features and one of the most valuable ones is the transaction searches into TTW.
This will show you the operations that occurred under conditions that the user specifies, giving you the opportunity to drill down on the things that are more important and affecting system performance.
Besides that, the capability of analyzing each individual transaction captured to a very low-level detail (method call/line of code). This ability empowers the testing teams to provide more visibility to developers on how they can improve.
