-
Notifications
You must be signed in to change notification settings - Fork 885
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
Add pino.multistream #1004
Add pino.multistream #1004
Conversation
Source code imported from https://github.com/pinojs/pino-multi-stream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm okay with this if you are. I rather liked it being a separate module because we cold say "it exists, but we do not recommend it" and get out of undesirable issues. But I can see that we are not going to be able to get rid of this feature, so bringing into core probably makes sense.
Co-authored-by: James Sumners <[email protected]>
Co-authored-by: James Sumners <[email protected]>
Co-authored-by: James Sumners <[email protected]>
@jsumners @davidmarkclements could you take a final look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Source code imported from https://github.com/pinojs/pino-multi-stream.
Following up from the introduction of #1003 and #937, I think we can include this in pino as well.
A user might like to send the data to a remote transport and also write the logs to disk.
I plan to make
pino.multistream()
to be usable within a custom transport, so that we do not spawn up more than one thread.