From 8ba3fe5028e046d29bf3e2b08476a556ce9c8c6f Mon Sep 17 00:00:00 2001 From: Curtis Robert Date: Wed, 31 Jul 2024 09:47:43 -0700 Subject: [PATCH] Update .chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml --- .chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml b/.chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml index ed783b3c7047..0bb595219fe9 100644 --- a/.chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml +++ b/.chloggen/use-observed-timestamp-if-timestamp-is-missing.yaml @@ -17,7 +17,7 @@ issues: [34150] # Use pipe (|) for multiline entries. subtext: Some OpenTelemetry libraries do not send timestamp for logs, but they should always send - | the observed timestamp. In these cases the clickhouse exporter just stored a zero timestamp + | the observed timestamp. In these cases the ClickHouse exporter just stored a zero timestamp | to the database. This changes the behavior to look into the observed timestamp if the timestamp | is zero.