Introduce Instrumentation Scope Attributes

Implements OTEP 201: https://github.com/open-telemetry/oteps/blob/main/text/0201-scope-attributes.md

Another PR will opened against the https://github.com/open-telemetry/opentelemetry-proto
repository to add the necessary fields to the messages.

CHANGELOG.md

@@ -49,6 +49,9 @@ release.
 
 ### Common
 
+- Introduce Instrumentation Scope Attributes
+  ([#2579](https://github.com/open-telemetry/opentelemetry-specification/pull/2579))
+
 ## v1.11.0 (2022-05-04)
 
 ### Context

specification/logs/logging-library-sdk.md

@@ -37,10 +37,26 @@ Logging Library SDK contains the following components:
 
 Methods:
 
-- Get LogEmitter. Accepts the instrumentation scope name and version and returns
-  a LogEmitter associated with the instrumentation scope.
-- Shutdown.
-- ForceFlush.
+#### Get LogEmitter
+
+Accepts the following parameters: instrumentation scope name, optional version and
+attributes. Returns a LogEmitter associated with the parameters.
+
+The implementation MUST NOT return the same `LogEmitter` when called repeatedly with
+different values of parameters. The only exception to this rule is no-op `LogEmitter`, the
+implementation MAY return the same instance regardless of parameter values.
+
+It is unspecified whether or under which conditions the same or different
+`LogEmitter` instances are returned from this functions when the same
+(name,version,attributes) parameters are used.
+
+#### Shutdown
+
+TBD
+
+#### ForceFlush
+
+TBD
 
 LogEmitterProvider can be configured at startup time, to be associated with a
 Resource and with LogProcessor/LogExporter pipeline.

specification/metrics/api.md

@@ -140,13 +140,21 @@ This API MUST accept the following parameters:
   has a version (e.g. a library version). Example value: `1.0.0`.
 * [since 1.4.0] `schema_url` (optional): Specifies the Schema URL that should be
   recorded in the emitted telemetry.
+* [since 1.12.0] `attributes` (optional): Specifies the instrumentation scope attributes
+    to associate with emitted telemetry.
 
-Meters are identified by all of these fields.  When more than one
-Meter of the same `name`, `version`, and `schema_url` is created, it
-is unspecified whether or under which conditions the same or different
-`Meter` instances are returned.  The term *identical* applied to
-Meters describes instances where all identifying fields are equal.
-The term *distinct* applied to Meters describes instances where at
+Meters are identified by all of these parameters.
+
+The implementation MUST NOT return the same `Meter` when called repeatedly with
+different values of parameters. The only exception to this rule is no-op `Meter`, the
+implementation MAY return the same instance regardless of parameter values.
+
+It is unspecified whether or under which conditions the same or different
+`Meter` instances are returned from this function when the same
+(name,version,schema_url,attributes) parameters are used.
+
+The term *identical* applied to Meters describes instances where all identifying fields
+are equal. The term *distinct* applied to Meters describes instances where at
 least one identifying field has a different value.
 
 Implementations MUST NOT require users to repeatedly obtain a `Meter` with

specification/trace/api.md

@@ -128,9 +128,16 @@ This API MUST accept the following parameters:
   has a version (e.g. a library version). Example value: `1.0.0`.
 - [since 1.4.0] `schema_url` (optional): Specifies the Schema URL that should be
   recorded in the emitted telemetry.
+- [since 1.12.0] `attributes` (optional): Specifies the instrumentation scope attributes
+  to associate with emitted telemetry.
+
+The implementation MUST NOT return the same `Tracer` when called repeatedly with
+different values of parameters. The only exception to this rule is no-op `Tracer`, the
+implementation MAY return the same instance regardless of parameter values.
 
 It is unspecified whether or under which conditions the same or different
-`Tracer` instances are returned from this functions.
+`Tracer` instances are returned from this function when the same
+(name,version,schema_url,attributes) parameters are used.
 
 Implementations MUST NOT require users to repeatedly obtain a `Tracer` again
 with the same name+version+schema_url to pick up configuration changes.

specification/trace/sdk_exporters/non-otlp.md

@@ -75,3 +75,12 @@ OpenTelemetry Span's dropped links count MUST be reported as a key-value pair
 associated with the Span. The key name MUST be `otel.dropped_links_count`.
 
 This key-value pair should only be recorded when it contains a non-zero value.
+
+### Instrumentation Scope Attributes
+
+Exporters to formats that don't have a concept that is equivalent to the Scope
+will record the attributes at the most suitable place in their corresponding format,
+typically at the Span, Metric or LogRecord equivalent.
+
+If the same attribute is specified both at the Span/Metric/LogRecord and at the Scope
+then the attribute value at Span/Metric/LogRecord takes precedence.