[config/confighttp] Resolve the TODO on confighttp.go related to prefixing operations with component id.

[atoulme]

From confighttp.go:

	// Enable OpenTelemetry observability plugin.
	// TODO: Consider to use component ID string as prefix for all the operations.
	handler = otelhttp.NewHandler(
		handler,
		"",
		otelhttp.WithTracerProvider(settings.TracerProvider),
		otelhttp.WithMeterProvider(settings.MeterProvider),
		otelhttp.WithPropagators(otel.GetTextMapPropagator()),
		otelhttp.WithSpanNameFormatter(func(operation string, r *http.Request) string {
			return r.URL.Path
		}),
	)

I have tried to resolve this TODO once before with #9123

[enesonus]

Hi @atoulme I would like to work on this issue. Is there any recommended readings or some files to look at? From what I understand, the span name formatter function can be used as a tool to set the prefix but I couldn't really understand how to get the component ID.

[atoulme]

@enesonus go for it, not sure how to do it

[VihasMakwana]

@atoulme can you assign this to me, I'll take it up.

[mx-psi]

I think this can be removed from Collector v1, since we don't provide any stability guarantees for traces

[jade-guiton-dd]

What is the status of this issue @atoulme @VihasMakwana? I believe the scope is a bit unclear. Do we want to:

1. make confighttp set the component ID as the span name prefix automatically; or,
2. let users of confighttp set an arbitrary prefix for their component?

The original TODO seems to suggest 1, but this seems to have been abandoned in favor of 2 because the component ID is not available in the confighttp code.

If 2 is fine, then I believe this issue was already resolved by #11769, which allows users to use otelhttp.WithSpanNameFormatter themselves.

[atoulme]

I opened this issue to remove this TODO and get the component to stable state. The TODO predates my time with the project. It's been thorny to resolve as everybody ends up guessing what the comment means in the context of the time it was written at. I believe you neatly address it in your comment. I also believe 2. addresses the need.

Can we please remove this TODO and close this issue? Would you like to open a PR?

[jade-guiton-dd]

Alright, I'll do that.

[jade-guiton-dd]

FYI, I opened a PR (#12351) to add that prefix for the OTLP receiver (and other HTTP receivers will have to do the same independently).