-
Notifications
You must be signed in to change notification settings - Fork 301
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
Unique name for instrument logger #1914
Unique name for instrument logger #1914
Conversation
If we go that way there should be some tests added |
Codecov Report
@@ Coverage Diff @@
## master #1914 +/- ##
==========================================
- Coverage 68.92% 68.14% -0.78%
==========================================
Files 156 156
Lines 19924 19929 +5
==========================================
- Hits 13732 13581 -151
- Misses 6192 6348 +156 |
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.
this sounds like a good idea, especially since instrument loggers are per-instance.
and tests - yes :) i suggest just simple ones - actual name of the instrument logger and channel logger.
This is now replaced by #5297 which will ensure that the instrument_name is an extra attribute on the logrecord from the instrument LoggerAdapter |
This ensures that each instrument will have it's own logger so that messages can easily be filtered by instrument instance
An instrument will have a logger with a name of the form
module.path.to.instrument.classname-instancename
and in the same way a channel will have a logger with a name of the form
module.path.to.instrument.classname-instancename.channelclassname-channelinstancename
@Dominik-Vogel