fix(logger): unset CORVA_LOGGER.propagate = False
for OTel Log Sending (refs EE-31)
#90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale
refs https://github.com/corva-ai/otel/pull/37
refs https://corvaqa.atlassian.net/browse/EE-31
Unset the
CORVA_LOGGER.propagate = False
so the OTel handler will be able to collect those logs as well
Here details on what I learned for Python Logging:
logging.basicConfig()
logging.getLogger()
gets you the Root Loggerlogging.getLogger("name")
propagate = False
unless for very isolated / local needs - this way whatever needs to work with logs centrally can continue doing so from the Root loggerAside - here snippet to do experiments if you wish
This "wrongly" configures handlers for both Root and Child logger, and will print:
Changes
Unset the
CORVA_LOGGER.propagate = False
so the OTel handler will be able to collect those logs as well
TODO