-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Update Logs <> Traces correlation documentation for Opentelemetry #27884
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a fix for python and a suggestion
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Outdated
Show resolved
Hide resolved
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't able to replicate existing code... but I left a working way to inject the information
content/en/tracing/other_telemetry/connect_logs_and_traces/opentelemetry.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for .NET
…ntelemetry.md Co-authored-by: mhlidd <matthew.li@datadoghq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Mikayla 👋🏻 We have some branch naming conventions that we need for our CI to ensure that your content is building properly. Could you please close this PR, rename your branch so it contains that weirdly load-bearing slash, and then create a new PR with that branch? That's usually the easiest way to kick off the automations that we need, and then we can approve and get this merged in for you.
Hope that makes sense, and apologies for the inconvenience!
What does this PR do? What is the motivation?
This PR removes any reference to mapping 128bit Otel trace IDs to Datadog 64bit trace IDs, while still maintaining instructions for mapping Otel span IDs to Datadog span IDs.
This documentation is outdated, as 128bit trace IDs have been supported in the Datadog logs backend [for correlating logs and traces] for quite some time.
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment:Additional notes