honeybadger-elixir
honeybadger-elixir copied to clipboard
honeybadger-io
Elixir client for Honeybadger.
This branch restores #342. See the original PR for summary and initial discussion. Let's continue discussion on this new PR.
Bumps [dialyxir](https://github.com/jeremyjh/dialyxir) from 1.1.0 to 1.2.0. Changelog Sourced from dialyxir's changelog. Unreleased changes post [1.2.0] [1.2.0] - 2022-07-20 Added "github" formatter. Commits 04f1bda Bump version d38e42f feat: Adds a github...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Hello, I'm currently testing Phoenix LiveView as a solution for an application that will run on production environments, and I would like to have some security regarding the error reporting...
Hello, For some reason, HoneyBadger is sending `Phoenix.Router.NoRouteError` errors even when I inserted my `use Honeybadger.Plug` after the `use CoreWeb, :router` call. Phoenix version: 1.5.3 Honeybadger version: 0.15 Here is...
We had a customer that expected the `Logger.error` call to notify Honeybadger. It looks like it would be a trivial change to allow notifying on logger error calls. My question...
Honeybadger now supports [sending arguments](https://github.com/honeybadger-io/honeybadger-elixir/pull/115), however the cases where the arguments are actually available seem limited; see [this comment by @sorentwo](https://github.com/honeybadger-io/honeybadger-elixir/pull/115#issuecomment-350154494). We may be able to provide arguments more often...
I don't know if this is expected since it is the first time I used Honeybadger, but most of the errors I'm receiving are encapsulated inside `ErlangErrors`. For example this...
Honeybadger.Logger process starts in wrong environments and terminates/times out for no clear reason
Hi! I have an Elixir/Phoenix app using Honeybadger for error reporting and logging. During development (and I suspect occasionally in production) the server throws a `DBConnection.ConnectionError`. This happens from time...
I see that you can filter out parts of an exception, but I was wondering if there was a way to selectively ignore and not notify an entire exception. Use...
