Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Freshping (discontinued)
Score 7.4 out of 10
N/A
Freshping was a website uptime monitoring tool with free and enterprise editions, from Freshworks. The product is no longer available to new customers.
$11
per month, billed annually
Pricing
Amazon CloudWatch
Freshping (discontinued)
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
Blossom - 60 checks (can add more checks)
$11.00
per month, billed annually
Garden - 80 checks (can add more checks)
$36.00
per month, billed annually
Sprout
Free
50 checks (none additional)
Offerings
Pricing Offerings
Amazon CloudWatch
Freshping (discontinued)
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.
Every additional 10 checks - $8/month billed annually
More Pricing Information
Community Pulse
Amazon CloudWatch
Freshping (discontinued)
Features
Amazon CloudWatch
Freshping (discontinued)
Monitoring Tasks
Comparison of Monitoring Tasks features of Product A and Product B
Amazon CloudWatch
-
Ratings
Freshping (discontinued)
4.8
2 Ratings
48% below category average
Remote monitoring
00 Ratings
7.52 Ratings
Network device monitoring
00 Ratings
2.01 Ratings
Multiple Server Monitoring
00 Ratings
4.52 Ratings
Multi-device monitoring
00 Ratings
2.01 Ratings
Automated alerts and notifications
00 Ratings
8.02 Ratings
Management Tasks
Comparison of Management Tasks features of Product A and Product B
Amazon CloudWatch
-
Ratings
Freshping (discontinued)
8.0
1 Ratings
6% above category average
Policy-based automation
00 Ratings
8.01 Ratings
Reporting
Comparison of Reporting features of Product A and Product B
For out business we find that AWS Cloudwatch is good at providing real-time metrics for monitoring and analysing the performance and usage of our platform by customers. It is possible to create custom metrics from log events, such people adding items to a basket, checking out or abandoning their orders.
Freshing is well suited for user-facing systems, the systems they directly use. It also serves as nice eye-candy for them to look at. It does not monitor internal IT systems as well as we had hoped, so we use other tools to monitor those systems.
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 excellent at collecting logs. It's easy to set up. The viewing & querying part could be much better, though. The query syntax takes some time to get used to, & the examples are not helpful. Also, while being great, Log Insights requires manual picking of log streams to query across every time.
It's perfectly easy and straightforward to use. There's no need to read documentation, you just register and will surely be able to configure whatever monitor you want to set up. It's also very easy to use other features like the status page, reporting, alerts, etc.
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.
Grafana is definitely a lot better and flexible in comparison with Amazon CloudWatch for visualisation, as it offers much more options and is versatile. VictoriaMetrics and Prometheus are time-series databases which can do almost everything cloudwatch can do in a better and cheaper way. Integrating Grafana with them will make it more capable Elasticsearch for log retention and querying will surpass cloudwatch log monitoring in both performance and speed
We use Uptime Robot, and also some internal health checks, which report directly to our emails and chat applications. They all work "pretty fine," but unfortunately all of them have had some false positives or missed some minor downtime, so as for us, it doesn't add too much overhead, and we prefer to use several. I would say all the ones mentioned are good for the job.