Clarify how ObservedTimestamp field is set if unspecified (open-telem…

…etry#3385) This is a clarification that follows from how the data model is specified: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#field-observedtimestamp This was noticed in a comment on another PR: https://github.com/open-telemetry/opentelemetry-specification/pull/3383/files#r1164491423 Co-authored-by: jack-berg <[email protected]>
carlosalberto · Apr 14, 2023 · 9441be8 · 9441be8
1 parent 5cef159
commit 9441be8
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md
@@ -118,7 +118,8 @@ this API.
 The API MUST accept the following parameters:
 
 - [Timestamp](./data-model.md#field-timestamp)
-- [Observed Timestamp](./data-model.md#field-observedtimestamp)
+- [Observed Timestamp](./data-model.md#field-observedtimestamp). If unspecified the
+  implementation SHOULD set it equal to the current time.
 - The [Context](../context/README.md) associated with the `LogRecord`. The API
   MAY implicitly use the current Context as a default
   behavior.