PYIC-8652: opentelemetry layer uses batch processor #3427
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hugh-emerson
force-pushed
the
PYIC-8652
branch
from
94c4458 to
cca8f8f
Compare
|
DanCorderIPV
approved these changes
Sep 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
What changed
Use the "batch" processor, which along with the "decouple" processor means that the exporting is tied to the lambda lifecycle correctly.
https://opentelemetry.io/blog/2025/observing-lambdas/
Why did it change
We were getting a bunch of error logs during lambda instance teardown. While nothing seemed to actually get lost, it was noisy.
As a side effect, it might sometimes result in a performance gain in exchange for traces/metrics arriving later. But in my testing I still usually got the trace immediately so I anticipate little impact.
Issue tracking
Checklists