Fix instantiation of LoggerProvider to work in edge runtime#136
Open
sfishel18 wants to merge 1 commit into
Open
Fix instantiation of LoggerProvider to work in edge runtime#136sfishel18 wants to merge 1 commit into
sfishel18 wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
the root cause is open-telemetry/opentelemetry-js#4473, but it can be worked around by passing an empty `logRecordLimits` to the LoggerProvider constructor. fixes vercel#104
sfishel18
force-pushed
the
sfishel18/edge-logger-provider
branch
from
755fc69 to
d134528
Compare
ams3cf
added a commit
to ams3cf/vercel-otel
that referenced
this pull request
Jan 26, 2025
|
Can anyone look at this? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
the root cause is open-telemetry/opentelemetry-js#4473, but it can be worked around by passing an empty
logRecordLimitsto the LoggerProvider constructor.fixes #104