Require the SDK to provide custom ID generation

open-telemetry · Oct 20, 2020 · 704efba · 704efba
1 parent 507884f
commit 704efba
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -50,6 +50,8 @@ New:
 - Add Metric SDK specification (partial): covering terminology and Accumulator component
   ([#626](https://github.com/open-telemetry/opentelemetry-specification/pull/626))
 - Add `Shutdown` function to `*Provider` SDK ([#1074](https://github.com/open-telemetry/opentelemetry-specification/pull/1074))
+- Add requirement that the SDK provide custom generation of Trace IDs and Span IDs
+  ([#1006](https://github.com/open-telemetry/opentelemetry-specification/pull/1006))
 
 Updates:
 

diff --git a/specification/trace/sdk.md b/specification/trace/sdk.md
@@ -204,6 +204,12 @@ Note: Implementation-wise, this could mean that `Tracer` instances have a
 reference to their `TracerProvider` and access configuration only via this
 reference.
 
+The SDK MUST provide a mechanism for customizing the way IDs are generated for
+both the `TraceId` and the `SpanId`.
+
+The SDK should by default randomly generate the bytes for both the `TraceId` and
+the `SpanId`.
+
 ### Shutdown
 
 This method provides a way for provider to do any cleanup required.