OptionalassignOptionalexcludeOptional parameter for routing. It should implement interface of
parameters of NestJS built-in MiddlewareConfigProxy['forRoutes'].
https://docs.nestjs.com/middleware#applying-middleware
It can be used for both disabling automatic req/res logs and
removing request context from following logs. It works for all requests by
default. If you only need to turn off the automatic request/response
logging for some specific (or all) routes but keep request context for app
logs use pinoHttp.autoLogging field.
OptionalforOptional parameter for routing. It should implement interface of
parameters of NestJS built-in MiddlewareConfigProxy['forRoutes'].
https://docs.nestjs.com/middleware#applying-middleware
It can be used for both disabling automatic req/res logs and
removing request context from following logs. It works for all requests by
default. If you only need to turn off the automatic request/response
logging for some specific (or all) routes but keep request context for app
logs use pinoHttp.autoLogging field.
OptionalpinoOptional parameters for pino-http module
OptionalrenameOptional parameter to change property name context in resulted logs,
so logs will be like:
{"level":30, ... "RENAME_CONTEXT_VALUE_HERE":"AppController" }
OptionaluseOptional parameter to skip pino configuration in case you are using FastifyAdapter, and already configure logger in adapter's config. The Pros and cons of this approach are described in the FAQ section of the documentation:
Optional parameter to also assign the response logger during calls to
PinoLogger.assign. By default,assigndoes not impact response logs (e.g.Request completed).