plugsnag alternatives and similar packages
Based on the "Framework Components" category.
Alternatively, view plugsnag alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
-
-
-
-
-
-
-
dayron
A repository `similar` to Ecto.Repo that maps to an underlying http client, sending requests to an external rest api instead of a database -
-
rummage_phoenix
Full Phoenix Support for Rummage. It can be used for searching, sorting and paginating collections in phoenix. -
phoenix_token_auth
Token authentication solution for Phoenix. Useful for APIs for e.g. single page apps. -
-
-
access pass
provides a full user authentication experience for an API. Includes login,logout,register,forgot password, forgot username, confirmation email and all that other good stuff. Includes plug for checking for authenticated users and macro for generating the required routes. -
-
Votex
Implements vote / like / follow functionality for Ecto models in Elixir. Inspired from Acts as Votable gem in Ruby on Rails -
-
trailing_format_plug
An elixir plug to support legacy APIs that use a rails-like trailing format: http://api.dev/resources.json -
plug_canonical_host
PlugCanonicalHost ensures that all requests are served by a single canonical host.
WorkOS - The modern identity platform for B2B SaaS
Do you think we are missing an alternative of plugsnag or a related project?
README
Plugsnag
Report errors in your Plug stack or whatever to Bugsnag, because that's a super great place to send your errors.
Installation/Usage
Just throw it in your deps in your mix.exs:
defp deps do
[{:plugsnag, "~> 1.4.0"}]
end
Then you'll need to configure it with your API key as per the bugsnag-elixir docs.
To use the plug, use it in your router. For example in an Phoenix app:
defmodule YourApp.Router do
use Phoenix.Router
use Plugsnag
# ...
end
If you want to define your own handle_errors functions using Plug.ErrorHandler, then you can call Plugsnag.handle_errors/{2,3} directly.
defmodule YourApp.Router do
use Phoenix.Router
use Plug.ErrorHandler
# ...
defp handle_errors(conn, assigns) do
Plugsnag.handle_errors(conn, assigns)
# do your own handling
end
end
Filtering Parameters and Headers
By default, the BasicErrorReportBuilder will filter out password parameters from error reports sent to Bugsnag. You can customize this list inside your configuration:
config :plugsnag, filter: [params: ~w(password password_confirmation super_sekrit), headers: []]
Customizing error reporting
You can also customize how an error is sent to bugsnag-elixir by passing your
own custom ErrorReportBuilder with the :error_report_builder option.
defmodule YourApp.Router do
use Phoenix.Router
use Plugsnag, error_report_builder: YourApp.ErrorReportBuilder
# ...
end
defmodule YourApp.ErrorReportBuilder do
@behaviour Plugsnag.ErrorReportBuilder
def build_error_report(error_report, conn) do
error_report
|> Plugsnag.BasicErrorReportBuilder.build_error_report(conn)
|> put_user_info(conn)
end
defp put_user_info(error_report, conn) do
current_user = conn.assigns[:current_user]
user_info = %{
id: current_user.id
}
%{error_report | user: user_info}
end
end