Status: Stable A logical unit of software with which the emitted telemetry can be associated. It is typically the developer’s choice to decide what denotes a reasonable instrumentation scope. The most common approach is to use the name and version of the instrumentation library, with any additional identifying information as part of the scope’s attributes. Other software components can be used too to get name, version and additional attributes, e.g. a module, a package, a class or a plugin.| OpenTelemetry
Status: Stable This document defines the stability guarantees offered by the OpenTelemetry clients, along with the rules and procedures for meeting those guarantees. In this document, the terms “OpenTelemetry” and “language implementations” both specifically refer to the OpenTelemetry clients. These terms do not refer to the specification or the Collector in this document. Each language implementation MUST take these versioning and stability requirements, and produce a language-specif...| OpenTelemetry
This document defines some terms that are used across this specification. Some other fundamental terms are documented in the overview document. User Roles Application Owner The maintainer of an application or service, responsible for configuring and managing the lifecycle of the OpenTelemetry SDK. Library Author The maintainer of a shared library which is depended upon by many applications, and targeted by OpenTelemetry instrumentation. Instrumentation Author The maintainer of OpenTelemetry i...| OpenTelemetry
