Software · head to head
CloudWatch vs Raygun
The short version
- Each has a real cost: CloudWatch the free tier covers 5 GB of log ingestion and 10 custom metrics a month, after which log ingestion is $0.50 per GB from 5 to 30 GB; Raygun crash Reporting error data is retained for 180 days and Real User Monitoring sessions for only 60 days; longer retention is Enterprise only
- They diverge on capability: CloudWatch covers Metrics collection, Raygun covers Crash reporting.
Where they differ
Only the attributes on which CloudWatch and Raygun actually diverge.
| Attribute | CloudWatch | Raygun |
|---|---|---|
| Founded | 2006 | 2011 |
Identical on both: starting price (Free), pricing model (usage-based), free tier (Yes), platforms (Web, Api), user rating (Not yet rated), category (Unknown).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in CloudWatch
- Metrics collection
- Log aggregation
- Dashboards
- Alarms and notifications
Only in Raygun
- Crash reporting
- Real user monitoring
- Performance tracking
- Source maps
Both cover
- API
- Webhooks
- REST
- Web support
- Api support
What people use each for
The jobs each tool is most often brought in to do.
CloudWatch
- Metrics and log collection for AWS workloadsnot Raygun
- Alarming on thresholds across AWS servicesnot Raygun
- Querying logs with Logs Insightsnot Raygun
- Live tailing logs during an incidentnot Raygun
- Distributed tracing alongside X-Raynot Raygun
Raygun
- Crash and error reporting for web, mobile and backend applicationsnot CloudWatch
- Real user monitoring of front end page load and session performancenot CloudWatch
- Application performance monitoring with request level tracesnot CloudWatch
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
CloudWatch
- The free tier covers 5 GB of log ingestion and 10 custom metrics a month, after which log ingestion is $0.50 per GB from 5 to 30 GB
- Custom metrics are $0.30 each for the first 10,000, so instrumenting broadly gets expensive before volume discounts apply
- Each custom dashboard beyond the free three is $3 a month
- Alarms are billed at $0.10 per alarm metric a month, with high-resolution alarms costing more
- Log storage beyond the free 5 GB is $0.03 per GB per month on top of the ingestion charge
Raygun
- Crash Reporting error data is retained for 180 days and Real User Monitoring sessions for only 60 days; longer retention is Enterprise only
- Crash Reporting, Real User Monitoring and APM are billed as three separate products, each metered on its own unit of errors, sessions or traces
- A Real User Monitoring session ends after 30 minutes of inactivity, so a single visit spanning breaks is billed as several sessions
- Usage beyond the plan allowance is billed on demand at $0.001 per error and $0.002 per session or trace
- Enterprise plan pricing is custom with no published rate
Pricing, plan by plan
CloudWatch
Free- FreeFree
- Metrics collection
- Log aggregation
- Dashboards
Raygun
Free- FreeFree
- Crash reporting
- Real user monitoring
- Performance tracking
Which should you pick?
Choose CloudWatch if
- You need metrics collection.
- You want to start without paying.
- You work on Web, Api.
- You also want log aggregation.
Choose Raygun if
- You need crash reporting.
- You want to start without paying.
- You work on Web, Api.
- You also want real user monitoring.
Questions people ask
- Is CloudWatch or Raygun better?
- Neither clearly leads. CloudWatch starts at Free and Raygun at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, CloudWatch or Raygun?
- CloudWatch starts at Free and Raygun at Free.
- Does CloudWatch or Raygun run on more platforms?
- Both run on Web, Api, so platform support will not decide this one for you.
- Can I use CloudWatch for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is CloudWatch best used for?
- CloudWatch is most often used for metrics and log collection for aws workloads, alarming on thresholds across aws services, querying logs with logs insights, live tailing logs during an incident. Of those, metrics and log collection for aws workloads and alarming on thresholds across aws services are not what Raygun is typically brought in for.
- What can CloudWatch do that Raygun cannot?
- CloudWatch covers Metrics collection, Log aggregation, Dashboards, Alarms and notifications. Raygun covers Crash reporting, Real user monitoring, Performance tracking, Source maps. Both handle API, Webhooks, REST, Web support.
Related pages
Keep looking
Other head to heads
- CloudWatch vs Elastic Stack
- CloudWatch vs New Relic
- CloudWatch vs Datadog Logs
- CloudWatch vs Coralogix
- CloudWatch vs Grafana Loki
- CloudWatch vs Dynatrace
- CloudWatch vs InfluxDB
- CloudWatch vs Airbrake
- CloudWatch vs AppDynamics
- CloudWatch vs Axiom
- CloudWatch vs Azure Monitor
- CloudWatch vs Better Stack
- CloudWatch vs Bugsnag
- CloudWatch vs Dynatrace Logs
- CloudWatch vs Elastic
- CloudWatch vs Elastic APM
- CloudWatch vs Elasticsearch Service
- CloudWatch vs ELK Stack
- Raygun vs Elastic Stack
- Raygun vs New Relic
- Raygun vs Datadog Logs
- Raygun vs Coralogix
- Raygun vs Grafana Loki
- Raygun vs Dynatrace
- Raygun vs InfluxDB
- Raygun vs Airbrake
- Raygun vs AppDynamics
- Raygun vs Axiom
- Raygun vs Azure Monitor
- Raygun vs Better Stack
- Raygun vs Bugsnag
- Raygun vs Dynatrace Logs
- Raygun vs Elastic
- Raygun vs Elastic APM
- Raygun vs Elasticsearch Service
- Raygun vs ELK Stack


