Merge HTTP instrumentation

[MrAlias]

The existing othttp and httptrace instrumentation need to be merged into a generalized instrumentation package to work with the standard library's net/http package.

• supports propagation of context.
• includes an http.Handler wrapper that will create spans and metric events for received requests.
  • Add semantic conventions for HTTP metrics opentelemetry-specification#739
• well documented.
• is a versioned module.
• likely needs to follow the naming scheme outline in the contrib repo: go.opentelemetry.io/otel/instrumentation/net/http

[MrAlias]

Relates to #940 (breaking into own module).

[MrAlias]

It seems to follow that this should be moved to the contrib repository. We have opensource libraries as well as stdlib library instrumentation support there. It seems like a good idea to consolidate everything into a single location.

[Aneurysm9]

I've created open-telemetry/opentelemetry-go-contrib#158 to relocate this instrumentation. The naming convention in contrib would lead me to think that the net/http and net/httptrace instrumentations should remain separate. Thoughts?

[MrAlias]

I've created open-telemetry/opentelemetry-go-contrib#158 to relocate this instrumentation. The naming convention in contrib would lead me to think that the net/http and net/httptrace instrumentations should remain separate. Thoughts?

The httptrace package in stdlib is a subpackage to net/http. Should we follow that structure as well? Not sure if there are implementation specific details that would prevent that structure, but it seems like it would be a decent approach to follow.

[MrAlias]

closing in favor of open-telemetry/opentelemetry-go-contrib#158