Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add execution-unit to glossary.md #2167

Merged
merged 3 commits into from
Nov 26, 2021
Merged

Add execution-unit to glossary.md #2167

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d0fe464
Add execution-unit to glossary.md
svrnm Nov 24, 2021
fa1cf8d
Merge branch 'main' into add-execution-unit-to-glossary
yurishkuro Nov 24, 2021
b07be24
Merge branch 'main' into add-execution-unit-to-glossary
carlosalberto Nov 26, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specification/compatibility/opentracing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
yurishkuro marked this conversation as resolved.
Show resolved Hide resolved
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.

Expand Down
2 changes: 1 addition & 1 deletion specification/context/context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
5 changes: 5 additions & 0 deletions specification/glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down Expand Up @@ -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
Expand Down