-
Notifications
You must be signed in to change notification settings - Fork 230
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 a logger #62
add a logger #62
Conversation
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.
👍 LGTM
api/lib/opentelemetry/logger.rb
Outdated
|
||
module OpenTelemetry | ||
class << self | ||
attr_accessor :logger |
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.
would it make more sense to put it to https://github.com/open-telemetry/opentelemetry-ruby/blob/2a22a85e09a2c4823a804d71481c3e4cc606f5fd/api/lib/opentelemetry.rb which already includes similar things and it's on top level also ?
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.
we could for sure. I started this thinking we would subclass Logger
but I didn't see any reason at the moment.
any opinions @fbogsany ?
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.
Nope, no opinions.
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.
lets see what everyone thinks. I'm ok either way.
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 moved it in
👀 |
Given the design of having no runtime impact, I thnk that error conditions will end up being eaten and not reported. While I don't think the user of the library will need to handle the cases directly it'd be good know if for instance they screwed up the header for propagation etc etc.
@fbogsany