Update otel_instrumentation.md with mapping requirements - #39854
Merged
Conversation
adding mapping requirements to Otel instrumentation documentation
Contributor
Preview links (active after the
|
hestonhoffman
left a comment
hestonhoffman
left a comment
Collaborator
There was a problem hiding this comment.
One small style edit
…ion.md Co-authored-by: Heston Hoffman <heston.hoffman@datadoghq.com>
hestonhoffman
approved these changes
Sep 11, 2026
ZStriker19
approved these changes
Sep 11, 2026
revised wording
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
3 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.
What does this PR do? What is the motivation?
adding mapping requirements to Otel instrumentation documentation specifically that for a span to be generated it requires one of a list of attributes.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.