Identify the instrumentation package within the scope

[MrAlias]

Currently, the scope for instrumentation (the Tracer name used) is set loosely around the target package of the instrumentation:

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/database/sql/probe.go

Line 45 in f29abc7

const instrumentedPkg = "database/sql"

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/github.com/gin-gonic/gin/probe.go

Line 45 in f29abc7

const instrumentedPkg = "github.com/gin-gonic/gin"

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/google.golang.org/grpc/probe.go

Line 69 in f29abc7

return "google.golang.org/grpc"

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/google.golang.org/grpc/server/probe.go

Line 68 in f29abc7

return "google.golang.org/grpc/server"

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/net/http/server/probe.go

Line 43 in f29abc7

const instrumentedPkg = "net/http"

opentelemetry-go-instrumentation/internal/pkg/instrumentation/bpf/net/http/client/probe.go

Line 66 in f29abc7

return "net/http/client"

These do not adequately identify the instrumentation library being used to produce the telemetry.

Proposal

1. Update the instrumentation names to have a prefix of go.opentelemetry.io/auto/.
2. Unify any client/server distinction (this distinction is made via the span kind)

For example:

• "go.opentelemetry.io/auto/database/sql"
• "go.opentelemetry.io/auto/github.com/gin-gonic/gin"
• "go.opentelemetry.io/auto/google.golang.org/grpc"
• "go.opentelemetry.io/auto/net/http"

[MrAlias]

2. Unify any client/server distinction (this distinction is made via the span kind)

This cannot be done without modifying the Manager logic. It assumes a unique identifier from each probe and uses the LibraryName to do this.

[MrAlias]

2. Unify any client/server distinction (this distinction is made via the span kind)

This cannot be done without modifying the Manager logic. It assumes a unique identifier from each probe and uses the LibraryName to do this.

The manifest being proposed in #419 can solve this issue. It can contain a unique identifying name the manager can use as well as the scope name.