Docs: Describe how to manually configure open telemetry #48071
Merged
Conversation
This file contains 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
jankaifer
changed the title
timneutkens
previously approved these changes
Apr 9, 2023
feedthejim
approved these changes
Apr 11, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It's currently not clear that
@vercel/otelis just a simple wrapper when you are trying things out. So I added an excellent example of how to instrument create an OpenTelemetry setup.The only FUD I have here is that people won't skip that
Manual OpenTelemetry setupand try to understand it. But I try to describe this at the beginning of that section.I'll also try to update
@vercel/otelreadme to be more transparent on what it does.