Unify instrumentation *Provider options

[XSAM]

Resolves #213

[XSAM]

I encounter a problem that beego cannot use its instrumentation name since it uses net/http instrumentation as its internal implements.

opentelemetry-go-contrib/instrumentation/github.com/astaxie/beego/beego.go

Lines 69 to 73 in 6b66176

	httpOptions := []otelhttp.Option{
	otelhttp.WithTracerProvider(cfg.traceProvider),
	otelhttp.WithMeterProvider(cfg.meterProvider),
	otelhttp.WithPropagators(cfg.propagators),
	}

---

Should we add a option WithInstrumentationName for net/http to temporary change its instrumentation name when initial?

[MrAlias]

I encounter a problem that beego cannot use its instrumentation name since it uses net/http instrumentation as its internal implements.

opentelemetry-go-contrib/instrumentation/github.com/astaxie/beego/beego.go

Lines 69 to 73 in 6b66176

	httpOptions := []otelhttp.Option{
	otelhttp.WithTracerProvider(cfg.traceProvider),
	otelhttp.WithMeterProvider(cfg.meterProvider),
	otelhttp.WithPropagators(cfg.propagators),
	}

Should we add a option WithInstrumentationName for net/http to temporary change its instrumentation name when initial?

No, I don't think that is needed. This sounds like the correct behavior. It should be the library that is providing the instrumentation that is the name of the tracer. I think the way it is setup is correct based on my understanding of the OpenTelemetry specification.

[MrAlias]

Looks good overall. Mostly question about naming and keeping around old Tracer fields.

[MrAlias]

Related: open-telemetry/opentelemetry-go#1101

[MrAlias]

Looks good, thanks for the detailed work 😄

Only requests are to unexport Tracers and Meters, but this could be a follow on PR.

[MrAlias]

🚀