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's the recommended way to use the module? #63

Open
VladimirMikulic opened this issue Dec 2, 2022 · 4 comments
Open

What's the recommended way to use the module? #63

VladimirMikulic opened this issue Dec 2, 2022 · 4 comments

Comments

@VladimirMikulic
Copy link

VladimirMikulic commented Dec 2, 2022

Hi, I was wondering what's the recommended way to use this module to create a transport?

pino-abstract-transport repo

Screenshot_20221202_053951

getpino.io/#/docs/transports

Screenshot_20221202_054007

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!

@jsumners
Copy link
Member

jsumners commented Dec 2, 2022

I believe the documentation you have provided via a screenshot is quite clear. What do you not understand of it?

@VladimirMikulic
Copy link
Author

Thanks for the fast response @jsumners. Yes, examples are clear, but which one should be used? :)
Should I use example from pino-abstract-transport (without sonic-boom lib) or example from getpino.io (with sonic-boom lib)?

@jsumners
Copy link
Member

jsumners commented Dec 3, 2022

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.

@LeoBLMitz

This comment was marked as spam.

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

3 participants