Skip to content

🪞 12267 - docs: fix broken source links in instrumentation guides - #12399

Open
mhlidd wants to merge 2 commits into
masterfrom
community-pr-12267
Open

🪞 12267 - docs: fix broken source links in instrumentation guides#12399
mhlidd wants to merge 2 commits into
masterfrom
community-pr-12267

Conversation

@mhlidd

@mhlidd mhlidd commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

This PR mirrors the changes from the original community contribution to enable CI testing with maintainer privileges.

Original PR: #12267
Original Author: @vaibhav8a
Original Branch: vaibhav8a/dd-trace-java:fix-broken-doc-links

Closes #12267


This is an automated mirror created to run CI checks. See tooling/mirror-community-pull-request.sh for details.

Current-tree links: google-http-client -> google-http-client-1.19, and
dd-java-agent/testing -> dd-java-agent/instrumentation-testing.

Pinned-SHA links at 5307b46 are deliberately left on the old path,
since that snapshot predates the module rename.
@mhlidd
mhlidd requested a review from a team as a code owner September 3, 2026 14:56
@mhlidd mhlidd added the tag: community Community contribution label Sep 3, 2026
@mhlidd
mhlidd requested review from daniel-mohedano and removed request for a team September 3, 2026 14:56
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

  • Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

@datadog-datadog-prod-us1 datadog-datadog-prod-us1 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: PASS

More details

The six changed links point to files and directories that exist in this branch.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Datadog Autotest · Commit 3af1814 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

@mhlidd
mhlidd enabled auto-merge September 3, 2026 15:00
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 13.95 s 13.94 s [-0.7%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent 12.93 s 12.96 s [-1.0%; +0.5%] (no difference)
startup:petclinic:appsec:Agent 17.66 s 17.43 s [+0.4%; +2.2%] (maybe worse)
startup:petclinic:iast:Agent 17.41 s 17.59 s [-1.8%; -0.2%] (maybe better)
startup:petclinic:profiling:Agent 16.78 s 17.29 s [-7.3%; +1.4%] (no difference)
startup:petclinic:sca:Agent 17.60 s 17.50 s [-0.3%; +1.5%] (no difference)
startup:petclinic:tracing:Agent 16.66 s 16.73 s [-1.4%; +0.5%] (no difference)

Commit: c4cb3e97 · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 16:52:44 UTC ℹ️ Start processing command /merge


2026-09-03 16:52:49 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 17:04:28 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for f852ba7:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 17:08:08 UTC ℹ️ Start processing command /merge


2026-09-03 17:08:14 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 17:23:33 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for c318b30:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 17:24:55 UTC ℹ️ Start processing command /merge


2026-09-03 17:25:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 17:42:17 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for e6e34a0:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 19:02:20 UTC ℹ️ Start processing command /merge


2026-09-03 19:02:26 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 19:17:53 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 2a3563d:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 19:43:55 UTC ℹ️ Start processing command /merge


2026-09-03 19:44:00 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 19:53:21 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for e40a3a1:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 19:54:33 UTC ℹ️ Start processing command /merge


2026-09-03 19:54:39 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).


2026-09-03 20:03:43 UTCMergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 49a40a9:

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

  • Investigate the failures and when ready, re-add your pull request to the queue!
  • If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
  • Any question, go check the FAQ.
Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
@mhlidd
mhlidd added this pull request to the merge queue Sep 3, 2026
@dd-octo-sts

dd-octo-sts Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/merge

@gh-worker-devflow-routing-ef8351

gh-worker-devflow-routing-ef8351 Bot commented Sep 3, 2026

Copy link
Copy Markdown

View all feedbacks in Devflow UI.

2026-09-03 20:25:40 UTC ℹ️ Start processing command /merge
Use /merge -c to cancel this operation!


2026-09-03 20:25:45 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

Use /merge -c to cancel this operation!


⏳ Building merge commit 09a1292278 in pipeline 2188930506706971696...

@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tag: community Community contribution tag: no release notes Changes to exclude from release notes type: documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants