From d29bdef27df1ca044eb35ceb29ed24b5c7f23d3b Mon Sep 17 00:00:00 2001 From: Tigran Najaryan Date: Wed, 12 Apr 2023 14:23:08 -0400 Subject: [PATCH] Clarify how ObservedTimestamp field is set if unspecified 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 --- specification/logs/bridge-api.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/specification/logs/bridge-api.md b/specification/logs/bridge-api.md index 2a51cedf69b..0768a511a5a 100644 --- a/specification/logs/bridge-api.md +++ b/specification/logs/bridge-api.md @@ -122,7 +122,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.