Span name for http server spans should include http.method.

[gouthamve]

Current spec defines the span name as the route, for example, /users/:userID?.

But having the http.method in the span name helps a lot, imo: GET /users/:userID?.

Prompted by open-telemetry/opentelemetry-go-contrib#3040

[cyrille-leclerc]

I support this proposal as REST architectures rely on the verb (GET, PUT, DELETE) to convey the sense of the action performed on the resource identified by its URI.
GET /users/:userID, PUT /users/:userID and DELETE /users/:userID are completely different operations with completely different code execution paths.
For this reason, I support the idea that the name of an HTTP span should be ${http.method} ${http.route}

[jsuereth]

I'm also supportive of this change.

[trask]

if we make this change, does it makes sense to also change the fallback (when there's no http.route available) from "HTTP {http.method}" to just "{http.method}"?

this would have the nice symmetry:

• "{http.method} {http.route}" if route is available
• "{http.method}" if route is not available

[blumamir]

I support this change too.

It also happens many times that the route is / (just one slash). In these cases, the current span name is just /, and I think changing it to GET / gives context to what we are looking at.

[arielvalentin]

if we make this change, does it makes sense to also change the fallback (when there's no http.route available) from "HTTP {http.method}" to just "{http.method}"?

this would have the nice symmetry:

• "{http.method} {http.route}" if route is available
• "{http.method}" if route is not available

if we make this change, does it makes sense to also change the fallback (when there's no http.route available) from "HTTP {http.method}" to just "{http.method}"?

this would have the nice symmetry:

• "{http.method} {http.route}" if route is available
• "{http.method}" if route is not available

👍🏼 👍🏼 👍🏼 in favor!