From 5122dee04786fd0f0d4627c356400d37c58ca515 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Wed, 24 Jul 2024 17:10:29 +0200 Subject: [PATCH] Use event.name in Event Data model (#4157) --- specification/logs/event-api.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/specification/logs/event-api.md b/specification/logs/event-api.md index 5180a21ca3b..9a769f498a0 100644 --- a/specification/logs/event-api.md +++ b/specification/logs/event-api.md @@ -47,9 +47,10 @@ logs to have a common format within that structure. When OpenTelemetry instrumentation emits logs, those logs SHOULD be formatted as Events. All semantic conventions defined for logs MUST be formatted as Events. -The Event format is as follows. All Events have a `name` attribute, and all -Events with the same `name` MUST conform to the same schema for both their -`Attributes` and their `Body`. +The Event format is as follows. All Events have a +[`event.name` attribute](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/events.md), +and all Events with the same `event.name` MUST conform to the same schema for +both their `Attributes` and their `Body`. ## Event API use cases