A Crystal client and integration layer for the Sentry error reporting API.
Raven.cr is an unofficial Crystal client for Sentry, a popular error tracking and monitoring platform. It allows Crystal developers to capture exceptions, log events, and send them to Sentry for real-time debugging and performance monitoring. The library integrates seamlessly with Crystal's logging system and popular web frameworks.
Crystal developers building web applications or services who need robust error tracking and monitoring capabilities. It's particularly useful for teams using frameworks like Kemal, Amber, or Lucky.
Developers choose Raven.cr because it provides a native, feature-complete Sentry client for Crystal, with framework integrations, async support, and a dedicated crash handler—filling a gap in the Crystal ecosystem for professional error monitoring.
Raven is a Crystal client for Sentry
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built-in support for Kemal, Amber, Lucky, Sidekiq.cr, and action-controller, allowing seamless error tracking in popular Crystal ecosystems without custom glue code.
Configurable async callbacks enable non-blocking error reporting, with examples for background jobs like Sidekiq.cr to maintain application performance.
External binary crash handler captures unhandled exceptions and segfaults, addressing a gap in Crystal's native error handling for production robustness.
Dedicated Log backend intercepts Crystal's standard log entries to record breadcrumbs or capture exceptions, enhancing debugging with minimal code changes.
Automatically activates only when SENTRY_DSN is set, preventing accidental error reports in development and simplifying environment-based setup.
As a community-maintained project, it may not keep pace with Sentry's official SDK updates, potentially missing new features or timely security patches.
Requires compiling and running a separate binary wrapper, adding steps to the build and deployment process compared to integrated solutions.
Sensitive data like POST bodies and cookies are not reported by default, which might hinder debugging unless explicitly configured, as noted in the README.