Is it possible to rename "instrumentation library" to "instrumentation scope"?

[tigrannajaryan]

This initially came from a discussion about introducing Logger Name.

While discussing the issue during the spec SIG meeting we came to a conclusion that the intent for "instrumentation library" was actually to have an "instrumentation scope".

The "instrumentation library" is currently used throughout the spec API and SDK. We want to explore if it is possible to rename "instrumentation library" to "instrumentation scope" without breaking existing stability guarantees.

This issue is a questions for the maintainers of this repo: are we able to do this in a non-breaking manner?

Note: this should be only done if it is not a breaking change. We must continue honouring our stability guarantees.

Warning: please don't make the actual change yet. We need to confirm first that it is possible to make this change everywhere before moving forward.

Spec issue recorded here: open-telemetry/opentelemetry-specification#2203

[MrAlias]

It is not going to be possible to rename "instrumentation library" to "instrumentation scope" without introducing a breaking change. There is the SDK type itself,

opentelemetry-go/sdk/instrumentation/library.go

Line 25 in 2b7c650

type Library struct {

As well as things like the read-only span interface,

opentelemetry-go/sdk/trace/span.go

Line 68 in 099df58

InstrumentationLibrary() instrumentation.Library

Changing these names will be breaking changes that would violate our stability guarantees.

It might be possible to add new types, options, and methods, and deprecate the old ones. I would have to probably go through the changes a bit more carefully if we wanted to go this route, but I'm not sure it would serve us in the long run.

[tigrannajaryan]

It appears the conclusion of many SDKs is that this is not a possible change. Closing. Thanks for checking.