Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Logz.io
Score 7.0 out of 10
Small Businesses (1-50 employees)
Logz.io in Boston offers their enterprise-grade log analytics application, oriented towards providing data security and eliminating the need for capacity management.
$0
1 day of log retention.
Pricing
Amazon CloudWatch
Logz.io
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
Log Management - Community
$0
1 day of log retention.
Log Management - Pro
$.92
per ingested GB. 7 days retention.
Distributed Tracing - Pro
$5
Per million spans.
Infrastructure Monitoring - Pro
$12
per month per 1000 time-series metrics.
Log Management - Enterprise
Custom
Cloud SIEM - Enterprise
from $1.49
per ingested GB. Price includes Logz.io Log Management
Offerings
Pricing Offerings
Amazon CloudWatch
Logz.io
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
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.
—
More Pricing Information
Community Pulse
Amazon CloudWatch
Logz.io
Considered Both Products
Amazon CloudWatch
Verified User
Anonymous
Chose Amazon CloudWatch
We use Cloudwatch for simpler monitoring, but these metrics and logs often feed into bigger ecosystems across our organization. The metrics and logs in Cloudwatch allow our developers quick and easy access to the data they need whilst easily integrating the same data into more …
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 …
In comparison to its competitors, Amazon CloudWatch is efficient, reliable, and has a fast response time, and it maximizes an application's life while also providing the best load balance and storage. The services that Amazon CloudWatch provides are far better and cheaper for …
We have also tested with SolarWinds NPM, and Zoho Monitors. They seemed to work fine and setup was not as involved as Amazon services, JSON, etc. However, the issue of upgrades made the other solutions incur more downtime overall for maintenance and software upgrades via the …
I think there is no alternative of [Amazon] CloudWatch service. However it provides lot of glue points which you can use to show different metrics, trigger events and update your dashboards.
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 …
We found that CloudWatch is the best solution to use with AWS services in terms of cost and ease of integration with AWS infrastructure services. While Elasticsearch is better at aggregating application-level metrics, CloudWatch wins out in its capabilities to tightly integrate …
CloudWatch is the minimum viable product that is used as your baseline. Once you graduate beyond the basic needs, there is a wide range of tools from other AWS partners that go well above and beyond. However the cost of those tools is typically considerably more.
We thought about using Logstash for capturing our data. But we encountered several configuration issues, so as I mentioned before, if you're using AWS, the best way to do this is using the service they offer, as you don't encounter configuration problems. This is why I consider …
I think Amazon has put more efforts to develop AWS CloudWatch features to monitor each kind of AWS service you can use instead of Dynatrace One Agent that just can monitor some variables of Computing services and FaaS, unless Dynatrace One Agent integration with AWS CloudWatch …
Out of the box monitoring which compliments workloads implemented from infrastructure as code so we have standardized metrics across all our monitoring for our AWS workloads. Also incredibly easy to implement via the console which can be done in minutes oppose to hours of …
We choose Amazon CloudWatch because, first, we use AWS and we need a monitoring tool. That is why we considered CloudWatch as soon as we started deploying AWS services to our company. Second, CloudWatch is a great, handy tool to monitor our services. Its strength is obvious …
Currently, we only tried and used Cloud Watch, but for AWS it is perfect. Since this is an Amazon product monitoring Amazon services, integration is great. If we decide in the future to move away from AWS, we would reconsider changing alarm monitoring. AWS can be costly …
Amazon CloudWatch is fully integrated into your existing AWS account, and provides easy hooks into several different services to make a cohesive infrastructure. Unfortunately, using other services will not allow you to get into the weeds to do everything Amazon CloudWatch can …
CloudWatch is incredibly cheap compared to new relic and much more intuitive and easy to use than Nagios. It requires no setup, expertise, or otherwise extensive knowledge to use.
We used to use Miscosoft Azure, however when we came across Amazon CloudWatch, and all the features it can provide, it seemd no brainer to switch. We transitioned from Azure to CloudWatch within 2 years of using Azure, And may not go back. Hopefully Amazon will keep adding more …
Amazon CloudWatch is great in terms of the CloudWatch Logs feature, it integrates easily with other AWS services (CloudFormation, S3, Lambda, etc.) and is reasonably low cost, so it was a no-brainer for that area. For alerting, CloudWatch didn't offer much in the way of …
I feel that CloudWatch will always remain the backbone of log analytics, events, and alarms. However, we can use other products in conjunction with it for better log analytics and monitoring. In my organization, we also ingest logs from CloudWatch to Splunk and ELK. This way we …
They offer the same function but logz.io commercial value is lower and can be adopted if company wanted just to meet baseline requirements of iso 27001 security controls. The basic function for centralize logs management and allow the feature of log collection for easy audit, …
Graylog and Microsoft System Center lacks infrastructure management and logging, proper analytics is done only on Logz.io. The customer support is also really great for Logz.io, we are really pleased with their support and timely action. The migration was also easy and took us …
Chosen before any other software for its versatility and speed to immediately stop any failure that may impair the operation of our applications, also their prices are very fair and it is very easy to work with it. On the other hand, other software such as FortiSIEM is very …
Director Of Information Technology & Data Management
Chose Logz.io
Logz.io is more affordable, less work to maintain, and has more features. It was an easy choice. After my last team had to manage their own ELK stack, this was a no brainer. It helps us be focused on our core competencies.
It is more focused in its approach which makes it really good for aggregating and analyzing logs. It has been way more helpful than New Relic APM for us. Data dog is nice but has some different focuses as well.
If you use any AWS services, CloudWatch is the natural choice to monitor & troubleshoot your workload. Thankfully, for most AWS services, CloudWatch is either built-in or very easy to set up. However, being proficient in browsing & tracking the log events would take some training & practice. Having some experienced people on the team would help immensely, especially in spreading the skill to the rest of the team.
It is appropriate for companies that focus on developing extremely simple applications. The great visibility it provides makes it ideal to avoid problems that may affect the entire business or company thanks to the fact that it is capable of emitting dozens of alerts in a short time. Sometimes the search behavior becomes slow and inefficient, which can be uncomfortable.
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.
Alerting - Logz.io allows you to set up numerous alerts and define the specific conditions to trigger these alerts, such as the number of occurrences over a specific period of time and severity.
Notifications - The supported integrations with Slack and OpsGenie make it easy to set up alerts to specific groups or users, like those in a particular Slack room or OpsGenie group. This is good to reduce noise and limit initial notifications to those who really need to get it.
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.
Although the tool itself is easy to integrate and is readily available for use, it has its limitations. The key limitations of cloudwatch are with respect to cost incurred on log retention and log querying. While for key use cases this is sufficient, for more advanced use cases, Amazon CloudWatch doesn't work out. Also, obviously it is tightly coupled with AWS, which makes you look away if you need a single tool for all monitoring
Am really exited to use the reports generated especially AWS Cost and Usage Reports function tracks your AWS usage and provides estimated charges associated with your account so that we can reduce the data costs to a greater extend. This integration allows you to ship logs from your AWS Cost and Usage Reports to your Logz.io account.More amazing features awaits you in Logz.io account.
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.
In the past, my team has been able to get in contact with Logz.io quickly and easily to address our questions about the product to see if it could fully meet all our needs. Some of the features we needed at the time were not available, but were on the Logz.io team's roadmap to implement in the future. I found their team to be friendly, professional, and helpful
We use Cloudwatch for simpler monitoring, but these metrics and logs often feed into bigger ecosystems across our organization. The metrics and logs in Cloudwatch allow our developers quick and easy access to the data they need whilst easily integrating the same data into more prominent platforms for wider analysis, including Service desk support, SecOps, and ITOps monitoring within the organization.
Graylog and Microsoft System Center lacks infrastructure management and logging, proper analytics is done only on Logz.io. The customer support is also really great for Logz.io, we are really pleased with their support and timely action. The migration was also easy and took us hardly a day to set up and run the solutions.