HTTP server span naming inconsistent across languages

[jkwatson]

We should have a more prescriptive semantic conventions for HTTP server span naming. In a brief look at 3 different languages: node, python, and java, I found disparities:

Java: /hello
Python: /hello
Node: GET /hello

[additional data needed for other languages...please provide]

The spec does not provide enough prescriptive guidance on this issue at the moment, leading to a possibly confusing experience for end-users in a polyglot environment.

[ocelotl]

I asked Claude to review this issue and Claude suggests it be closed with this explanation:

Asks for prescriptive HTTP server span naming, which the HTTP semantic conventions now provide explicitly (span name MUST be {method} {http.route}, falling back to {method} when route is unavailable). That semantic-convention area was also migrated to open-telemetry/semantic-conventions, so any remaining refinement belongs there rather than the spec repo. No comments or open cross-references remain on this 2021 issue.

To guard against a mistaken suggestion, Claude then independently re-verified this conclusion:

Confirmed: HTTP semconv now prescriptively defines server span name as {method} {http.route} with fallback to {method} (and MUST NOT use URI path), directly resolving the cross-language inconsistency the 2021 issue raised; area migrated to semantic-conventions repo, no comments/cross-refs remain.

Claude evaluated this issue with medium confidence that it can be closed.

Claude has classified this issue as resolved.

The intention of this comment is to make it easier for a human being to review this issue before making a decision.

[svrnm]

Closing this, as this is now a semantic conventions issue, and requirements seem to be satisfied, if this is incorrect, please open a new issue on the semantic conventions repository.