Skip to content
New issue

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

What transports & pipelines we should include? #1

Open
H4ad opened this issue May 25, 2024 · 0 comments
Open

What transports & pipelines we should include? #1

H4ad opened this issue May 25, 2024 · 0 comments

Comments

@H4ad
Copy link
Owner

H4ad commented May 25, 2024

By default pino will output to stdout using SonicBoom at https://github.com/pinojs/pino/blob/main/lib/tools.js#L330-L336

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>.

@H4ad H4ad changed the title What transports we should include? What transports & pipelines we should include? May 25, 2024
@H4ad H4ad pinned this issue May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant