search

honeybadger-io / honeybadger-python

Send Python and Django errors to Honeybadger.
https://www.honeybadger.io/
MIT License
15 stars 25 forks source link

Include method arguments in backtrace #90

Open joshuap opened 3 years ago

joshuap commented 3 years ago

I believe Python makes method arguments available to each stack frame in the traceback. Is that correct? If so, I'd like to include the arguments in the Honeybadger backtrace, as we do for Elixir (see filter_args option).

This feature should be enabled when a new filter_args is set to false. The default should be true so that args are not included by default. We'll ship this as an opt-in feature in the next minor version; I may enable it by default in the next major version.

Also, what other data is available in the traceback/stack frame that we could be including?

Resources

Front logo Front conversations

remstone7 commented 1 year ago

this is related 👍 to #122

Kelvin4664 commented 10 months ago

Addressed with #123

joshuap commented 9 months ago

@Kelvin4664 @subzero10 I don't think this was addressed with #123, because this issue was to add local variables at the stack frame level in the traceback, whereas #123 added local variables for the top-level call. Is that right? If so, we should keep this open, assuming it's technically feasible.

subzero10 commented 9 months ago

@Kelvin4664 @subzero10 I don't think this was addressed with #123, because this issue was to add local variables at the stack frame level in the traceback, whereas #123 added local variables for the top-level call. Is that right? If so, we should keep this open, assuming it's technically feasible.

Oh, you are right! Good catch!