-
Notifications
You must be signed in to change notification settings - Fork 9
Feature Request: Encode stack traces as an array #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Interesting idea - definitely not opposed to it, but would like to hear what others have to say about it. |
FWIW, structlog does something similar
https://www.structlog.org/en/stable/api.html#structlog.processors.JSONRenderer |
That's good to know thanks @edgarrmondragon |
Thanks! I will implement it. |
nhairs
added a commit
that referenced
this issue
Feb 4, 2025
close #35 This PR add options to encode stack information into an array. - If `exc_info_as_array` is True (Defualt: False), formatter encode `exc_info` into an array. - If `stack_info_as_array` is True (Defualt: False), formatter encode `stack_info` into an array. ### Test plan - run tests --------- Co-authored-by: Nicholas Hairs <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Uh oh!
There was an error while loading. Please reload this page.
Hi! I often use this library. It is very useful and I love it.
When the logger using
JsonFormatter
logs exceptions, the output is like this.The stack trace is hard to read. It should be more readable like this.
Proposal
stack_trace_as_array
toJsonFormatter
.False
for backward compatibility.True
, The formatter encodes stack traces as an array.If you agree this feature, I will create PR.
The text was updated successfully, but these errors were encountered: