We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
By default pino will output to stdout using SonicBoom at https://github.com/pinojs/pino/blob/main/lib/tools.js#L330-L336
stdout
SonicBoom
Should we include more transports, like:
Should we include pipelines like:
Also, the way to expose those built-in transports can be something like:
setOptions({ transport: { target: 'node:logging/transports/pretty', }, })
Basically we can group/expose the transports via node:logging/transports/<name> and the pipelines via node:logging/pipelines/<name>.
node:logging/transports/<name>
node:logging/pipelines/<name>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
By default pino will output to
stdout
usingSonicBoom
at https://github.com/pinojs/pino/blob/main/lib/tools.js#L330-L336Should we include more transports, like:
Should we include pipelines like:
Also, the way to expose those built-in transports can be something like:
Basically we can group/expose the transports via
node:logging/transports/<name>
and the pipelines vianode:logging/pipelines/<name>
.The text was updated successfully, but these errors were encountered: