Restore DSM end-to-end latency troubleshooting content - #39734
Open
arjunguhaswe wants to merge 1 commit into
Open
Restore DSM end-to-end latency troubleshooting content#39734arjunguhaswe wants to merge 1 commit into
arjunguhaswe wants to merge 1 commit into
Conversation
Restores the 'End-to-end latency metric doesn't look accurate' section that was removed from the Data Streams Monitoring docs, so the in-app Troubleshooting link from the APPROXIMATION badge resolves to real content instead of the bare index page. Also fixes the section's instrumentation link to point at the Go/Java manual instrumentation docs instead of a circular link back to the setup section. Co-Authored-By: Warp <agent@warp.dev>
Contributor
Preview links (active after the
|
Contributor
|
🔗 Commit SHA: 8eb7899 | Docs | View more details | Give us feedback! |
hestonhoffman
approved these changes
Sep 4, 2026
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
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?
The in-app APPROXIMATION badge on the DSM "Top latency contributors" widget links to
/data_streams/#end-to-end-latency-metric-doesnt-look-accurate, but that section was deleted from the docs in March 2025 (PR #27986) without migrating its content, leaving the link pointing at the bare index page.This PR restores the "End-to-end latency metric doesn't look accurate" section on the Data Streams Monitoring index page, with a heading that reproduces the anchor the in-app link expects. It also fixes the section's instrumentation link, which previously pointed back to the page's own Setup section instead of the Go/Java manual instrumentation docs.
No Jira ticket is attached yet; happy to add one if the team wants this tracked.
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.AI assistance
Investigated with Warp (Oz) to find the commit and PR that deleted the original troubleshooting content, then used it to draft the restored section and fix its broken instrumentation link.
Additional notes
Worth checking the DSM frontend for other in-app links to
/data_streams/#...anchors, since this same content removal may have broken more than one.Co-Authored-By: Warp agent@warp.dev