You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@tigrannajaryan
Ok, FWIW, we wanted to discuss this in our meeting at Wednesday, but it should not have been a problem for us, and a 1 minute task with suitable refactoring tools.
@tidal Thanks for checking. This change is not possible in other SDKs and we need it everywhere or nowhere, so we are forced to back off and close this.
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
The text was updated successfully, but these errors were encountered: