-
Notifications
You must be signed in to change notification settings - Fork 114
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 non-blocking send to kafka provider #149
Add non-blocking send to kafka provider #149
Conversation
7f8938a
to
8a228a0
Compare
8a228a0
to
a97fc6c
Compare
Hi @nemanjamikic, thanks for the contribution and sorry for the delay in answering. I am curious about the options What do you think? |
Hi @jcchavezs , thank you for responding to issue. |
Hi @nemanjamikic I have mixed feelings here. While I believe what you say it's true, I am ITOH not sure about the fact that one accept the Any input @adriancole @basvanbeek |
I don't see a technical problem to solve here only a documentation / expectation issue. I suggest we handle this by improving documentation and probably an example |
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.
Instead of importing the concern of Sarama configuration into the Zipkin Go package I'd much rather see a fix of documentation as well as addition of proper usage of this reporter in an example.
Closed in favour of #158. Still thanks a lot for the initiative @nemanjamikic! |
Because zipkin is not critical component if kafka producer queue is full all messages should be logged and ignored. This is optional feature.