-
Notifications
You must be signed in to change notification settings - Fork 878
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
Error Object Serialisation doesn't work #862
Comments
How are you passing in an error? |
I try to understand how pino works so I only write : |
The serializers only works if you prefix your object { err } would call the err serializer. |
I see. In case of a real application how me can manage that as we don't have control of generated errores? |
I don't understand, who is calling the logger then? |
If you don't know when something is logged I can't really help :(. Study your code. |
Ok. Thanks for your help |
I'm trying to understand how pino works, I look for documentation on internet but I found it difficult to find one which explains how to implement pino with code examples. If you know some links to help me, Could you give them to me please |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I'm just starting out using pino and I try to serialize error object but it doesn't work
this is the code I use:
const log = pino({ name: "pino", timestamp: pino.stdTimeFunctions.isoTime, level: "trace", serializers: { err: err => ({ type: err.type, message: err.message, stack: e.stack }) } })
Could you help me please?
Thanks
The text was updated successfully, but these errors were encountered: