Should HTTP semantic conventions say anything about nested spans?

[trask]

For example:

• Should nesting of HTTP server spans not be allowed?

• Should nesting of HTTP client spans be allowed?

[scheler]

Just asking out of curiousity. What is the guidance on the span kind proxies should use for the span they emit, if they emit only one span? Or are they required to emit 2 spans, one server and one client?

[trask]

Discussed in today's semconv meeting, and closing because the issue primarily because nesting is more of a "cross-instrumentation" issue which should be handled at a higher level (specifically see open-telemetry/oteps#172)

[trask]

Just asking out of curiousity. What is the guidance on the span kind proxies should use for the span they emit, if they emit only one span? Or are they required to emit 2 spans, one server and one client?

hey @scheler, I don't think there's any specific guidance yet for this case, I'd suggest emitting 2 spans myself, as that would fit the current conventions (and probably the majority of backends).