Robert Pająk

Per https://github.com/open-telemetry/opentelemetry-specification/issues/3210 we could simply create a new resource detector that sets the service.name resource based on the name of the entry assembly.

FYI here is a code that we have in .NET Automatic Instrumentation: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/42c51e6273df04cfe54e08ae073939cf515c2e93/src/OpenTelemetry.AutoInstrumentation/Configurations/ResourceConfigurator.cs#L51

Superseded by https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/1644

I reviewed all code with `catch` and I have not found any issue.

The other idea is to only use `DependsOn` and one could use `--skip` to Skip all dependencies or some specified ones.

There is no guarantee if the instruments provided by this package will be stable. Each version (and implementation of Go) can produce different metrics. Right now the https://pkg.go.dev/runtime/metrics doc even...

I am reopening it and assigning to myself. However, I guess I will have to time to look at it in about a month 😬 @terev Can you make update...

@terev I think the "missing feature" of using `otelhttp.NewMiddleware` is that the route tags (like `assert.Contains(t, attrs, attribute.String("http.route", "/user/:id"))`) would be lost.

This issue is no longer valid.

@charleskorn Can you update the PR? Sorry for the delay.