You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The stack info renderer is very useful to add stack traces, but unfortunately it keeps the traces of the actual logging itself.
In the funciton _find_first_app_frame_and_name there is support for finding the first relevant frame by adding ignored modules to be skipped, but this isn't exposed to the StackInfoRenderer in any way.
Since we have our internal logging mechanism built upon structlog, it would be very benficial if we could add this module prefix to the skipped modules.
If it were added as a parameter when initializing the class, for example, we could define ignored modules and get a more refined and less noisy stack trace.
The text was updated successfully, but these errors were encountered:
The stack info renderer is very useful to add stack traces, but unfortunately it keeps the traces of the actual logging itself.
In the funciton
_find_first_app_frame_and_name
there is support for finding the first relevant frame by adding ignored modules to be skipped, but this isn't exposed to theStackInfoRenderer
in any way.Since we have our internal logging mechanism built upon structlog, it would be very benficial if we could add this module prefix to the skipped modules.
If it were added as a parameter when initializing the class, for example, we could define ignored modules and get a more refined and less noisy stack trace.
The text was updated successfully, but these errors were encountered: