From 48bdd23f687bde319618c1dfa2a7ac5c6ce83b0f Mon Sep 17 00:00:00 2001
From: Tigran Najaryan <4194920+tigrannajaryan@users.noreply.github.com>
Date: Fri, 10 Dec 2021 17:13:56 -0500
Subject: [PATCH] Clarify the semantics of the Log Timestamp field (#2183)

Contributes to https://github.com/open-telemetry/opentelemetry-specification/issues/1875

This is part 1 of the change. Part 2 will add the observed timestamp field. See the issue
for the discussion and the description of the source vs observed timestamps.
---
 specification/logs/data-model.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/specification/logs/data-model.md b/specification/logs/data-model.md
index 9e1fbe9b847..73ffafe2130 100644
--- a/specification/logs/data-model.md
+++ b/specification/logs/data-model.md
@@ -195,8 +195,9 @@ Below is the detailed description of each field.
 
 Type: Timestamp, uint64 nanoseconds since Unix epoch.
 
-Description: Time when the event occurred measured by the origin clock. This
-field is optional, it may be missing if the timestamp is unknown.
+Description: Time when the event occurred measured by the origin clock, i.e. the
+time at the source. This field is optional, it may be missing if the source
+timestamp is unknown.
 
 ### Field: `ObservedTimestamp`