Document OTel service-level DBM correlation - #38533
Open
pierreln-dd wants to merge 5 commits into
Open
Conversation
Add a Correlation levels section to the OTel + DBM guide distinguishing statement-level from service-level correlation, including the stored procedure limitation and the manual comment format needed to enable service-level correlation for OpenTelemetry setups. Add a callout to the Go tab of Connect DBM and APM warning about a latency regression when using full propagation mode with the pgx driver. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
pierreln-dd
changed the title
Contributor
Preview links (active after the
|
Remove reassurance-style phrasing and redundant restatements to match Datadog's straightforward, direct documentation voice. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
pierreln-dd
marked this pull request as ready for review
July 29, 2026 11:32
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
1 participant
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?
Adds documentation for OpenTelemetry service-level vs. statement-level APM<>DBM correlation, which wasn't previously covered in public docs.
Clarifies that statement-level correlation works automatically for OTel setups, but service-level correlation (Calling Services, Databases tab) requires a SQL comment with service metadata that OTel auto-instrumentation doesn't add by default. Documents the comment format needed to enable it manually, and notes that stored procedure calls aren't supported for correlation.
Merge instructions
Merge readiness:
Additional notes