Robert Pająk

I think that the Go Automatic Instrumentation should "by default" set the global providers and use them as well. On top of it, we should add a possibility to: 1....

@MrAlias @RonFed Now, I see your point. I think that may be worth exploring the support of instrumenting `nonRecordingSpan`.

SIG meeting: Moving it post-beta. There is no reason to delay the beta release so much.

@open-telemetry/go-instrumentation-maintainers, can you double-check if I have not missed any important reference in the issue description? Should someone wanting to document all env vars be able to find all env...

> If I remember correctly, Java/NodeJS auto instrumentations generate spans for Kafka/databases by default even though the semantic conventions are not stable yet. Same for .NET. The feedback we got...

> I imagine there are many users that want it on by default, but is there any data showing how do user's feel when those instrumentation libraries change their output...

I see that Java released 2.0 when they changed HTTP sem conv: https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/tag/v2.0.0

> @pellared have you introduced breaking changes to the telemetry output in any instrumentation? As far as I remember we the HTTP instrumentation had breaking changes in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/releases/tag/v1.3.0 The upcoming...

> @edeNFed would it be helpful to expose this as an option as well? Something like `WithAllInstrumentation`? > > That way any distribution of this project could make all the...

My personal preference is still to have experimental features as opt-in, but I think users should be able to enable all of them in a easy way. Maybe `WithExperimental` option...