add LoggerProvider force flush in Lambda function #441
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.
Issue #, if available:
The current Lambda instrumentation is missing a call to the loggerProvider.force_flush method, which can result in delayed or missing OTel logs in the Lambda environment due to Lambda freeze
Description of changes:
Adding LoggerProvider force flush in Lambda instrumentation.
Logging a debug log if the loggerProvider does not support force flush because the default global LoggerProvider is ProxyLoggerProvider in OpenTelemetry Python, will be replaced to SDKLoggerProvider only if user set environment variable
OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED = true
, which is not set in ADOT Lambda layer.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.