This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Excessively verbose req
serializer?
#14
Comments
something must have changed with the serializer in pino-http this isn't right |
wait what if you don't specify any serializers.. I know you need to for noir I suspect what's happening here is the asReqValue isn't being applied because it's lost from the serializers think we need do a slight API change
|
@davidmarkclements are you working on this? |
not currently - feel free the parallel work in hapijs/hapi-pino#34 looks to be a helpful reference point we need to do this in pino-http instead, so this issue should be moved |
I suppose the fix here will be updating the |
yes! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Consider this example app:
Issuing a simple
GET
to the endpoint results in a tremendous amount of logged data for thereq
object:expand for output log
This does not seem right, particularly considering the example output in the documentation here. I'm not an
express
guy, is this normal? Also notice that this output makes redacting material doubly complicated (e.g.req.headers
andreq.rawHeaders
).The text was updated successfully, but these errors were encountered: