-
Notifications
You must be signed in to change notification settings - Fork 13
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's the recommended way to use the module? #63
Comments
I believe the documentation you have provided via a screenshot is quite clear. What do you not understand of it? |
Thanks for the fast response @jsumners. Yes, examples are clear, but which one should be used? :) |
You should use whichever applies to your situation. Unless @mcollina can confirm that the example in this module's readme needs to be updated to match what is in the Pino docs. |
This comment was marked as spam.
This comment was marked as spam.
can this one be answered please? what's best to use in what case, why almost none transports use sonic-boom 🤔 cc @mcollina |
Hi, I was wondering what's the recommended way to use this module to create a transport?
pino-abstract-transport repo
getpino.io/#/docs/transports
I checked the source of pino-seq-transport, pino-elasticsearch and pino-sentry-transport and none of them make use of
sonic-boom
.Is transports page on getpino.io out of date or? Do I need
sonic-boom
stuff?Thanks!
The text was updated successfully, but these errors were encountered: