-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Move sarama initialization to scraper start method #3104
Move sarama initialization to scraper start method #3104
Conversation
from create scraper to start scraper method
Codecov Report
@@ Coverage Diff @@
## main #3104 +/- ##
==========================================
+ Coverage 91.59% 91.62% +0.02%
==========================================
Files 486 486
Lines 23515 23525 +10
==========================================
+ Hits 21539 21554 +15
+ Misses 1469 1461 -8
- Partials 507 510 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Resolved |
@bogdandrutu it would be great to get this merged before the next release |
* move client and admin initialization from create scraper to start scraper method * update integration test * update integration err msg * fix client close before return * fix for comments * update CHANGELOG.md
Updates #3104 Signed-off-by: Bogdan Drutu <[email protected]>
Updates #3104 Signed-off-by: Bogdan Drutu [email protected]
Description: scrapers are updated to initialize sarama client and admin in
Start
instead of thecreateMetricsReceiver
method. This way, the receiver is immediately created (instead of contacting broker(s) first). If no brokers are reachable, the receiver will fail to start. refLink to tracking Issue:
Testing: Unit test and integration test updated.
Documentation: