[chore] Mention JavaAgent v2.0.0 default behaviour

[devurandom]

Changes

HTTP semantic convention stability migration docs ¹ do not mention that the JavaAgent v2.0.0 already defaults to the new, stable behaviour ², which could lead to people believing they have to set OTEL_SEMCONV_STABILITY_OPT_IN=http when they don't.

This does not change an actual convention, thus I believe it does not need a changelog entry.

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

Footnotes

1. https://opentelemetry.io/docs/specs/semconv/non-normative/http-migration/ ↩

2. https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.0.0 ↩

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: devurandom / name: Dennis Schridde (24f3717, 2a4c2bf)

[arminru]

@open-telemetry/java-instrumentation-maintainers FYI

[trask]

@devurandom a related discussion has been taking place in #534, can you review that issue? thanks

[devurandom]

a related discussion has been taking place in #534, can you review that issue?

Thanks for the hint. I was not aware of that issue.

My PR is (to a limited degree) addressing his point in #534 (comment): I point out that, if you're using Java agent v2.0.0 or later, the migration does not apply to you.

I do not feel qualified to address the wider-scope suggestions he points out, like #534 (comment) to create a table for all supported languages, that fully address the issue and could close it.

[trask]

I point out that, if you're using Java agent v2.0.0 or later, the migration does not apply to you.

if you are upgrading from Java agent 1.x to 2.x, I think it does apply to you

[lmolkova]

thanks for the clarification!

should this text belong in the javaagent docs? I believe this doc is intended for instrumentation authors and telemetry backends rather than the end-users of specific instrumentation.

I don't mind having it here either, but then I think we need a section for instrumentation-specific behavior that would initially contain Java instrumentation agent.

Curious what @trask thinks.

[trask]

should this text belong in the javaagent docs?

I think that would probably be a better place, until we solve the more general questions in #534

[devurandom]

Similar to @TylerHelmuth in #534, I would probably not have stumbled upon this info in the Java agent docs, since I was (via web search and general reading about metrics and their attributes) coming from the semconv docs.

[trask]

I wonder if this whole section above is adding to the confusion. It was a good part of the blog post, but I wonder if the document here should just focus on the summary of changes?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.