Software · head to head
Dynatrace Logs vs Raygun
The short version
- Each has a real cost: Dynatrace Logs log ingest and processing is billed at $0.20 per GiB, separately from retention and from query; 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: Dynatrace Logs covers Log analysis, Raygun covers Crash reporting.
Where they differ
Only the attributes on which Dynatrace Logs and Raygun actually diverge.
| Attribute | Dynatrace Logs | Raygun |
|---|---|---|
| Pricing model | subscription | usage-based |
| Founded | 2005 | 2011 |
Identical on both: starting price (Free), 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 Dynatrace Logs
- Log analysis
- AI-powered insights
- Metrics integration
- Automated root cause
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.
Dynatrace Logs
- Ingesting and processing application and infrastructure logsnot Raygun
- Querying logs alongside traces and metrics in one platformnot Raygun
- Log driven alerting within an existing Dynatrace deploymentnot Raygun
Raygun
- Crash and error reporting for web, mobile and backend applicationsnot Dynatrace Logs
- Real user monitoring of front end page load and session performancenot Dynatrace Logs
- Application performance monitoring with request level tracesnot Dynatrace Logs
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Dynatrace Logs
- Log ingest and processing is billed at $0.20 per GiB, separately from retention and from query
- Querying logs is charged in addition to ingest, either pay per query or as bundled queries
- Log analytics requires the same annual platform commitment as the rest of the Dynatrace platform
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
Dynatrace Logs
Free- FreeFree
- Log analysis
- AI-powered insights
- Metrics integration
Raygun
Free- FreeFree
- Crash reporting
- Real user monitoring
- Performance tracking
Which should you pick?
Choose Dynatrace Logs if
- You need log analysis.
- You want to start without paying.
- You work on Web, Api.
- You also want ai-powered insights.
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 Dynatrace Logs or Raygun better?
- Neither clearly leads. Dynatrace Logs 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, Dynatrace Logs or Raygun?
- Dynatrace Logs starts at Free and Raygun at Free.
- Does Dynatrace Logs or Raygun run on more platforms?
- Both run on Web, Api, so platform support will not decide this one for you.
- Can I use Dynatrace Logs for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Dynatrace Logs best used for?
- Dynatrace Logs is most often used for ingesting and processing application and infrastructure logs, querying logs alongside traces and metrics in one platform, log driven alerting within an existing dynatrace deployment. Of those, ingesting and processing application and infrastructure logs and querying logs alongside traces and metrics in one platform are not what Raygun is typically brought in for.
- What can Dynatrace Logs do that Raygun cannot?
- Dynatrace Logs covers Log analysis, AI-powered insights, Metrics integration, Automated root cause. Raygun covers Crash reporting, Real user monitoring, Performance tracking, Source maps. Both handle API, Webhooks, REST, Web support.
Related pages
More on Dynatrace Logs
Keep looking
Other head to heads
- Dynatrace Logs vs Elastic Stack
- Dynatrace Logs vs New Relic
- Dynatrace Logs vs Datadog Logs
- Dynatrace Logs vs Coralogix
- Dynatrace Logs vs Grafana Loki
- Dynatrace Logs vs CloudWatch
- Dynatrace Logs vs Dynatrace
- Dynatrace Logs vs InfluxDB
- Dynatrace Logs vs Airbrake
- Dynatrace Logs vs AppDynamics
- Dynatrace Logs vs Axiom
- Dynatrace Logs vs Azure Monitor
- Dynatrace Logs vs Better Stack
- Dynatrace Logs vs Bugsnag
- Dynatrace Logs vs Elastic
- Dynatrace Logs vs Elastic APM
- Dynatrace Logs vs Elasticsearch Service
- Dynatrace Logs vs ELK Stack
- Raygun vs Elastic Stack
- Raygun vs New Relic
- Raygun vs Datadog Logs
- Raygun vs Coralogix
- Raygun vs Grafana Loki
- Raygun vs CloudWatch
- 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 Elastic
- Raygun vs Elastic APM
- Raygun vs Elasticsearch Service
- Raygun vs ELK Stack


