Move performance to java agent, merge javadoc into API page

[jack-berg]

Resolves #5211.

An alternative to #5522 based on the conversation here:

• Move "Performance" page to "Zero-code Instrumentation -> Java -> Agent -> Performance"
• Merge "Javadoc" into "Record Telemetry with API", page from "../api-components/" to "../api/".

---

Previews

• https://deploy-preview-5590--opentelemetry.netlify.app/docs/languages/java/api/
• https://deploy-preview-5590--opentelemetry.netlify.app/docs/zero-code/java/agent/performance/

[jack-berg]

/fix:htmltest-config

[opentelemetrybot]

You triggered fix:htmltest-config action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/11808233847

[opentelemetrybot]

fix:htmltest-config was successful.

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

[chalin]

Works for me. @open-telemetry/docs-approvers any other feedback?

Once all checks are passing, of course ✅

[chalin]

Blocking until I figure out how best to manage the broken links in non-en pages.

[chalin]

(Edited to include a full list)

@jack-berg - there are broken links in this en page that need to be fixed:

docs/collector/deployment/agent/index.html
  target does not exist --- docs/collector/deployment/agent/index.html --> /docs/languages/java/api-components/#meterprovider
docs/zero-code/java/agent/performance/index.html
  target does not exist --- docs/zero-code/java/agent/performance/index.html --> ../sdk/#sampler
  hash does not exist --- docs/zero-code/java/agent/performance/index.html --> ../getting-started/#prerequisites
docs/languages/java/instrumentation/index.html
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#context-api
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#contextpropagators
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#contextpropagators
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#context
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#semantic-attributes
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#loggerprovider
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#logger
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#tracerprovider
  target does not exist --- docs/languages/java/instrumentation/index.html --> ../api-components/#meterprovider
docs/languages/java/sdk/index.html
  target does not exist --- docs/languages/java/sdk/index.html --> ../api-components/
  target does not exist --- docs/languages/java/sdk/index.html --> ../api-components/#opentelemetry
  target does not exist --- docs/languages/java/sdk/index.html --> ../api-components/#tracerprovider
  target does not exist --- docs/languages/java/sdk/index.html --> ../api-components/#meterprovider
  target does not exist --- docs/languages/java/sdk/index.html --> ../api-components/#loggerprovider
docs/concepts/instrumentation/libraries/index.html
  target does not exist --- docs/concepts/instrumentation/libraries/index.html --> /docs/languages/java/api-components/#contextpropagators
docs/languages/java/intro/index.html
  target does not exist --- docs/languages/java/intro/index.html --> ../api-components/
  target does not exist --- docs/languages/java/intro/index.html --> ../performance/
docs/languages/java/configuration/index.html
  target does not exist --- docs/languages/java/configuration/index.html --> ../api-components/
========================================================================
✘✘✘ failed in 40.707039223s
23 errors in 1988 documents

[jack-berg]

Blocking until I figure out how best to manage the broken links in non-en pages.

I've fixed all the links and believe there weren't any broken links in non-en pages

[svrnm]

LGTM, will wait for @chalin to re-review.

[chalin]

It seems like the non-en link-check failures were in en fallback pages.

LGTM

[chalin]

It seems that we need one more approval from @open-telemetry/java-approvers.

[jack-berg]

It seems that we need one more approval from @open-telemetry/java-approvers.

We've got an approval from java-approver @jaydeluca. Do we need a second? In the past, one java-approver approval has been enough. Not expressing an opinion on whether we should have one or two approvals required - just clarifying my understanding. 🙂

[chalin]

I'm not sure what the policy is; I'll let @svrnm chime in. Also, I don't see @jaydeluca listed in @open-telemetry/java-approvers, which matches what GH reported above:

[jack-berg]

Also, I don't see @jaydeluca listed in @open-telemetry/java-approvers, which matches what GH reported above:

Ah that's right. Yeah we have a bit of a weird thing going on where we have two partially independent / partially overlapping groups of approvers in the java SIG: @open-telemetry/java-approvers and @open-telemetry/java-instrumentation-approvers. Both groups are trusted collaborators in the Java SIG, but the @open-telemetry/java-instrumentation-approvers tend to contribute more to the opentelemetry-java-instrumentation repo while the @open-telemetry/java-approvers tend to contribute more to the opentelemetry-java repo.

In my head, the set of people trusted to approve java opentelemetry.io PRs is the superset of both groups, since the docs have much less strict delineation between content related to opentelemetry-java-instrumentation and opentelemetry-java.

Some instances where an approval from a @open-telemetry/java-instrumentation-approvers has been sufficient: #5471, #5275, #4966

[chalin]

Thanks for the explanation @jack-berg. That works for me. Adding this to the merge queue.

[trask]

In my head, the set of people trusted to approve java opentelemetry.io PRs is the superset of both groups

👍