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
It's currently hard to implement following behavior with pino-http:
Log request with headers, url, request params and other required info.
Process request and call log multiple times during the scope of request. Request params, headers, etc.. should NOT be included in these logs.
Log response. Request params, headers, etc... should NOT be added to this log.
It seems like with current functionality we can either add unnecessary metadata to every single log during scope of request (quietReqLogger=false) or add them at the end (quietReqLogger=true).
However, there is no way to easily do the opposite - to add all aditional info at start of request, and do only lightweight logging afterwards. It seems natural, that first log of request scope should include all the metadata (i..e what if request takes way longer than expected or it hangs somehow).
The text was updated successfully, but these errors were encountered:
manvydasu
changed the title
[Proposal] support for quietResLogger(similar to quietReqLogger)
[Proposal] support for quietResLogger (similar to quietReqLogger) - log full bindings at start of request instead at the end.
Jun 22, 2022
It's currently hard to implement following behavior with pino-http:
log
multiple times during the scope of request. Request params, headers, etc.. should NOT be included in these logs.It seems like with current functionality we can either add unnecessary metadata to every single log during scope of request (
quietReqLogger=false
) or add them at the end (quietReqLogger=true
).However, there is no way to easily do the opposite - to add all aditional info at start of request, and do only lightweight logging afterwards. It seems natural, that first log of request scope should include all the metadata (i..e what if request takes way longer than expected or it hangs somehow).
The text was updated successfully, but these errors were encountered: