Replace Sentry
Exception aggregation with stack traces, release tracking and alerting.
Why teams move off Sentry
Sentry is excellent and priced on event volume, which means a bad deploy is also an expensive one.
What you give up
Release health, performance tracing, source maps and cross-service context.
This directory says so when an engine only covers part of the job. A replacement that needs a caveat is still worth knowing about — it just should not surprise you in week three.
2 Rails engines that replace Sentry
-
Rails Performance
Covers the core of AnalyticsThe performance-monitoring half: slow endpoints, slow jobs, throughput. Not exception tracking.
Sentry → rails_performance
No ratings yet → -
Solid Errors
Covers the core of OperationsException capture, grouping and a dashboard. No release health, no performance tracing, no source maps.
Sentry → solid_errors
No ratings yet →
Questions
- Is there an open-source alternative to Sentry for Rails?
- Yes — Rails Performance and Solid Errors. Both mount into an application you already run, so there is no second deployment and no second database.
- What do I give up by replacing Sentry?
- Release health, performance tracing, source maps and cross-service context.
- How do I replace Sentry in a Rails app?
- Add rails_performance to your Gemfile, mount it in config/routes.rb at /rails/performance, and run its migrations. The whole integration is two lines and a migration.
- How much does replacing Sentry save?
- Sentry is priced from $26/mo. The engines here are open source, so the cost becomes the time to mount one and the resources it uses inside your existing application.
Same category
