-
Notifications
You must be signed in to change notification settings - Fork 1
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
Standardize Prometheus metrics using OTEL #55
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #55 +/- ##
==========================================
+ Coverage 98.34% 99.24% +0.89%
==========================================
Files 47 29 -18
Lines 1030 661 -369
==========================================
- Hits 1013 656 -357
+ Misses 17 5 -12 ☔ View full report in Codecov by Sentry. |
xprom/xkafkaprom/collector.go
Outdated
@@ -0,0 +1,230 @@ | |||
package xkafkaprom |
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.
Should we make the package name simply as xprom/xkafka
rather than xprom/xkafkaprom
?
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 want to avoid the name conflict while creating and configuring a producer/consumer.
Maybe we can use a convention like xprom*
- xpromkafka
, xpromdb
, xpromsql
etc.
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 have noticed this pattern in https://github.com/riverqueue/river
No description provided.