Skip to content

Restore DSM end-to-end latency troubleshooting content - #39734

Open
arjunguhaswe wants to merge 1 commit into
masterfrom
arjun.guha/dsm-restore-latency-troubleshooting-anchor
Open

Restore DSM end-to-end latency troubleshooting content#39734
arjunguhaswe wants to merge 1 commit into
masterfrom
arjun.guha/dsm-restore-latency-troubleshooting-anchor

Conversation

@arjunguhaswe

Copy link
Copy Markdown

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

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <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.
  • 🤖 New: Comment with /review to 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

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>
@arjunguhaswe
arjunguhaswe requested review from a team as code owners September 4, 2026 14:57
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@datadog-official

datadog-official Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Pipelines

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 8eb7899 | Docs | View more details | Give us feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants