switch opentelemetry span names for litestar from `/some/resource/123…

[xgemx]

In the base scenario open telemetry use scope.path as span.name param. But for endpoints with some id as a part of the route (for example /some/resource/123) there will be a span for every resource_id. First of all, that will be a problem for analytic of your spans. But the second one, it will garbage your span collector with unlimited span names. That's why this PR switch opentelemetry span names for litestar from /some/resource/123 to /some/resource/{resource_id}.

[vrslev]

It would be nice to see some tests.

[vrslev]

I think this kind of stuff should be done in Litestar itself though

[xgemx]

I think this kind of stuff should be done in Litestar itself though

Looks like it is more OpenTelemetry staff like FastAPI or Django instrumentation. But there is no Litestar instrumentation for OpenTelemetry yet.

Also I'm not sure, that this is excellent span name builder for any Litestar user, looks like this is more our vision of right span names. Decision for everybody must be more flexible and generic and I have no time to implement it right now.

[vrslev]

Method in span name is not compliant to the spec: open-telemetry/opentelemetry-python-contrib#3769

[vrslev]

let's remove methods from span names, and merge)

[vrslev]

Privately chatted, decided to keep the method in span name