I wrote this mainly for the need of better debugging in development, and never inspected live traffic on a production server.
If you balance your application across servers/workers and keep the log on a per-worker basis I think there shouldn't be a problem in doing so.
Otherwise - you could make a middleware that collects requests that require attention (response time above some threshold, non-200 status codes, errors).
Then you could "replay" the logger on those requests.
(You can't do it live, since you can't know in advance which requests will be of interest.)
Maybe I find a way to incorporate this into the project, so that you can use it out of the box :-)
I wrote this mainly for the need of better debugging in development, and never inspected live traffic on a production server.
If you balance your application across servers/workers and keep the log on a per-worker basis I think there shouldn't be a problem in doing so.
Otherwise - you could make a middleware that collects requests that require attention (response time above some threshold, non-200 status codes, errors).
Then you could "replay" the logger on those requests.
(You can't do it live, since you can't know in advance which requests will be of interest.)
Maybe I find a way to incorporate this into the project, so that you can use it out of the box :-)