== Rails-native failure investigation Rails Error Dashboard (RED) is an open-source, self-hosted Rails engine for investigating production exceptions without sending error data to a monitoring vendor. It groups errors and records request context and cause chains and, when enabled, breadcrumbs plus local and instance variables captured before Ruby unwinds the stack. == What it records * Rails and Ruby runtime health on the error record, refreshed on every captured occurrence: Active Record pool, Puma, background jobs, GC, memory, threads, file descriptors and system pressure * Built-in storm protection that progressively sheds expensive context and I/O during error floods while retaining useful exemplars and exact occurrence counts * Copy as RSpec, curl or LLM prompt; swallowed-exception detection; LLM observability without prompt capture; OpenTelemetry span export * Workflow, notifications (Slack, Email, Discord, PagerDuty, webhooks) and two-way issue sync with GitHub, GitLab, Codeberg and Linear * Rails-specific operational views: jobs, database, cache, Action Cable, Active Storage, Rack::Attack and deprecations == Running it Run RED with your application's database or an isolated error database, on PostgreSQL, MySQL/Trilogy or SQLite. The dashboard is translated into 11 languages (French native-reviewed; the rest machine-translated and awaiting native review). A self-hosted Sentry alternative that keeps error data in your own database. The gem is MIT and free forever. Supports Rails 7.0-8.1 and Ruby 3.2-4.0. Beta: APIs may change before 1.0. Live demo: https://rails-error-dashboard.anjan.dev Documentation: https://AnjanJ.github.io/rails_error_dashboard