Tracey Onim

Thank you @SophieDeBenedetto for the confirmation. I wanted to find out first from the members if its okay for the future blogs that I'm planning to write. I'm looking forward...

> @yukster good points. > > I _think_ that `use_logger: false` will also [prevent reporting crashes in SASL compliant processes](https://github.com/honeybadger-io/honeybadger-elixir#logger). > > It seems like `use_logger` may have dual responsibilities—I...

> > Kindly confirm my assumption if its true, does all SASL crashes fall under `[:sasl]` or `[:otp]` domain? If yes then I think ignoring only `[:elixir]` domain might help...

@sezaru I have tried reproducing the error with the phoenix and honeybadger version specified. Still, I'm unable to get the bug you are facing. Kindly confirm with me the Elixir...

The problem is that on my end everything seems to be working fine, it could be at least easier if we could reproduce the same error. I think the formatting...

> What we want to do is to be able to recognise which module has generated the issue. In the case of controllers it can be easily fetch from plug,...

I have found out, arguments are available when a FunctionClauseError is reported. Here is the [explanation](https://stackoverflow.com/questions/65406610/include-function-arguments-in-stack-trace-when-raising-error). With that, I have also found out that, the stack trace is been parsed...

> @TraceyOnim nice! > > So with #373 merged, what should the documentation say about `filter_args`? It still only works for `FunctionClauseError`, right? If that's the case, we should update...

> Another question: do you think it's possible to display args for other types of exceptions with some additional research/work in the future? Or should I close this issue after...

> @sorentwo I've been thinking, would it make sense to default to `filter_args = false` in the next major release, so that args are reported w/ `FunctionClauseError` by default? Great...