OTel Correlation Guides

[brett0000FF]

What does this PR do? What is the motivation?

Existing content was outdated and fragmented. This change unifies all correlation content into a set of guides.

• New: Correlate Data landing page
• New: Correlate DBM and traces
• New: Correlate metrics and traces
• Updated: Correlate logs and traces

Updates:

• Logs info was outdated and overcomplicated--customers should use trace_id now.
• DBM correlation info was missing.
• Unified Service Tagging info was missing (existed in a totally separate part of the docs).
• Metrics correlation info was hidden in host metrics documentation--create traces/metrics correlation page with initial info and link to host metrics to improve discoverability.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[github-actions]

📝 Documentation Team Review Required

This pull request requires approval from the @DataDog/documentation team before it can be merged.

Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes.

[github-actions]

Preview links (active after the build_preview check completes)

New or renamed files

• https://docs-staging.datadoghq.com/brett.blue/otel-correlation/opentelemetry/correlate/dbm_and_traces
• https://docs-staging.datadoghq.com/brett.blue/otel-correlation/opentelemetry/correlate/metrics_and_traces

Modified Files

• https://docs-staging.datadoghq.com/brett.blue/otel-correlation/opentelemetry/correlate/
• https://docs-staging.datadoghq.com/brett.blue/otel-correlation/opentelemetry/integrations/host_metrics
• https://docs-staging.datadoghq.com/brett.blue/otel-correlation/tracing/other_telemetry/connect_logs_and_traces/opentelemetry

[shanelhuang]

Looks good to me for the Trace and Metrics correlation page.

[brett0000FF]

@jade-guiton-dd - Thanks a ton for your detailed review! Super helpful. I've updated the guide and believe I've addressed all of your points. I'd appreciate if you could take another look when you have a moment.

• Updated the terminology throughout (for example, using "fields" instead of "attributes" where appropriate) and clarified how logging bridges work by converting logs into the OTel data model.
• Rewrote the "Scrape logs from files" section based on your feedback. It now uses the much more robust approach of manually injecting trace context with a standard JSON logger. Would appreciate your eyes on this update in particular.
• Defined the required format for trace_id and span_id.
• Expanded the Datadog Agent section to better explain the reliance on dd.trace_id and the need for manual remapping when not using the OTel Collector.

[jade-guiton-dd]

Looks good to me on the logs side.

[jade-guiton-dd]

I like these recommendations (logs through OTLP first, scraping w/ manual context injection second, and not even mentioning using an OTel console exporter), but I'd be interested in feedback from other OTel team members.

@dineshg13 you brought up concerns about performance for OTLP logs vs. scraping; do you think it's worth a mention?