From d0fe464cdc9885aa38d3410f1659829f0b786e0d Mon Sep 17 00:00:00 2001 From: svrnm Date: Wed, 24 Nov 2021 15:03:55 +0100 Subject: [PATCH] Add execution-unit to glossary.md --- specification/compatibility/opentracing.md | 2 +- specification/context/context.md | 2 +- specification/glossary.md | 5 +++++ 3 files changed, 7 insertions(+), 2 deletions(-) diff --git a/specification/compatibility/opentracing.md b/specification/compatibility/opentracing.md index d669a51632b..4a6ceb72ae9 100644 --- a/specification/compatibility/opentracing.md +++ b/specification/compatibility/opentracing.md @@ -126,7 +126,7 @@ MUST be done by the Shim layer in order to retain these invariants. Because of the previous requirement, a given OpenTelemetry `Span` MUST be associated with ONE AND ONLY ONE `SpanContext` Shim object at all times -for ALL execution units, in order to keep any linked `Baggage` consistent +for ALL [execution units](../glossary.md#execution-unit), in order to keep any linked `Baggage` consistent at all times. It MUST BE safe to get and set the associated `SpanContext` Shim object for a specified OpenTelemetry `Span` from different execution units. diff --git a/specification/context/context.md b/specification/context/context.md index 91c76b51c8c..64713713d69 100644 --- a/specification/context/context.md +++ b/specification/context/context.md @@ -21,7 +21,7 @@ Table of Contents ## Overview A `Context` is a propagation mechanism which carries execution-scoped values -across API boundaries and between logically associated execution units. +across API boundaries and between logically associated [execution units](../glossary.md#execution-unit). Cross-cutting concerns access their data in-process using the same shared `Context` object. diff --git a/specification/glossary.md b/specification/glossary.md index afe71ec5be4..0bf07a1ed27 100644 --- a/specification/glossary.md +++ b/specification/glossary.md @@ -27,6 +27,7 @@ Some other fundamental terms are documented in the [overview document](overview. * [Instrumented Library](#instrumented-library) * [Instrumentation Library](#instrumentation-library) * [Tracer Name / Meter Name](#tracer-name--meter-name) + * [Execution Unit](#execution-unit) - [Logs](#logs) * [Log Record](#log-record) * [Log](#log) @@ -153,6 +154,10 @@ This refers to the `name` and (optional) `version` arguments specified when creating a new `Tracer` or `Meter` (see [Obtaining a Tracer](trace/api.md#tracerprovider)/[Obtaining a Meter](metrics/api.md#meterprovider)). The name/version pair identifies the [Instrumentation Library](#instrumentation-library). +### Execution Unit + +An umbrella term for the smallest unit of sequential code execution, used in different concepts of multitasking. Examples are threads, coroutines or fibers. + ## Logs ### Log Record