Consider using go module paths for scope name in demos

[dashpole]

Problem Statement

I noticed the rolldice example has a single-word name for the meter and tracer:

opentelemetry-go/example/dice/rolldice.go

Lines 12 to 17 in ca93aae

	const name = "rolldice"
	var (
	tracer = otel.Tracer(name)
	meter = otel.Meter(name)
	logger = otelslog.NewLogger(name)

I haven't checked other examples, but IMO we should consider doing this across all of them.

Proposed Solution

Since many users will use this as a starting point for their code, would it make more sense to use a "real" scope name? E.g. go.opentelemetry.io/otel/example/dice?

Alternatives

Keep simpler names for samples

[dashpole]

Also, should we document the convention that the go import path of the library producing the telemetry should be used as the scope name?

[MrAlias]

Also, should we document the convention that the go import path of the library producing the telemetry should be used as the scope name?

SGTM. Only question is where should we document this? Package docs?

[MrAlias]

To complete this, the docs site will need to be updated as well.

[MrAlias]

Also, should we document the convention that the go import path of the library producing the telemetry should be used as the scope name?

We already document this directly for the Meter and Tracer:

• opentelemetry-go/trace/trace.go

  Lines 548 to 551 in d595dab

  	// The passed name needs to uniquely identify instrumentation code.
  	// Therefore, it is recommended that name is the Go package name of the
  	// library providing instrumentation (note: not the code being
  	// instrumented). Instrumentation libraries can have multiple versions,

• opentelemetry-go/metric/meter.go

  Lines 26 to 29 in d595dab

  	// A Meter should be scoped at most to a single package. The name needs to
  	// be unique so it does not collide with other names used by
  	// an application, nor other applications. To achieve this, the import path
  	// of the instrumentation package is recommended to be used as name.

We should add this to the LoggerProvider:

opentelemetry-go/log/provider.go

Lines 19 to 25 in d595dab

	// Logger returns a new [Logger] with the provided name and configuration.
	//
	// If name is empty, implementations need to provide a default name.
	//
	// Implementations of this method need to be safe for a user to call
	// concurrently.
	Logger(name string, options ...LoggerOption) Logger

@dashpole do you think this is adequate documentation?

[MrAlias]

We should add this to the LoggerProvider:

#5613

[dashpole]

@dashpole do you think this is adequate documentation?

yes, thank you!