Elixir client for reporting exceptions and logs to Rollbar, with automatic crash reporting for OTP processes.
Rollbax is an Elixir client library for the Rollbar error monitoring service. It allows Elixir applications to report exceptions, crashes, and logs to Rollbar, providing centralized error tracking and debugging insights. The library integrates with OTP processes and web frameworks like Phoenix to automate error reporting in production environments.
Elixir developers building production applications who need reliable error monitoring and crash reporting. It is particularly useful for teams using Phoenix, Plug, or OTP-based systems.
Rollbax offers a native Elixir integration with Rollbar, supporting automatic crash reporting for OTP processes and seamless integration with Phoenix and Plug. It is configurable for different environments and follows Elixir best practices.
Exception tracking and logging from Elixir to Rollbar
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically reports crashes from GenServers and Tasks, leveraging Elixir's concurrency model for robust production monitoring, as highlighted in the crash reports feature.
Provides built-in integrations for web applications, simplifying error reporting in Phoenix frameworks without extra setup, detailed in the Plug and Phoenix section.
Allows disabling or logging errors locally in non-production environments via the 'enabled' config, reducing noise and adapting to different deployment stages.
Configurable HTTP proxy setup for network-restricted environments, ensuring connectivity in corporate networks, as specified using hackney proxy options.
Rollbax.Logger is no longer a Logger backend and can cause crashes if misconfigured, indicating breaking changes and potential setup pitfalls, as warned in the README.
Tightly coupled with Rollbar's API, making migration to other error services cumbersome and requiring significant codebase changes, limiting flexibility.
Requires running tests with the '--no-start' flag to avoid configuration errors from missing access tokens, adding complexity to the development workflow.