From fcebfd2def995bd9f1139e49c5aa2dba57afb2ce Mon Sep 17 00:00:00 2001 From: Liudmila Molkova Date: Tue, 10 Dec 2024 18:35:05 -0800 Subject: [PATCH] Add `event_name` to logs proto (#600) * Add event_name to log proto --- CHANGELOG.md | 4 ++++ opentelemetry/proto/logs/v1/logs.proto | 14 ++++++++++++++ 2 files changed, 18 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 34eac7b3..6bac4f03 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,10 @@ The full list of changes can be found in the compare view for the respective release at . +### Added + +- logs: Add top-level `event_name` field to log records instead of `event.name` attribute. [#600](https://github.com/open-telemetry/opentelemetry-proto/pull/600) + ## 1.4.0 - 2024-11-20 ### Added diff --git a/opentelemetry/proto/logs/v1/logs.proto b/opentelemetry/proto/logs/v1/logs.proto index df91e3d1..261d2291 100644 --- a/opentelemetry/proto/logs/v1/logs.proto +++ b/opentelemetry/proto/logs/v1/logs.proto @@ -210,4 +210,18 @@ message LogRecord { // - the field is not present, // - the field contains an invalid value. bytes span_id = 10; + + // A unique identifier of event category/type. + // All events with the same event_name are expected to conform to the same + // schema for both their attributes and their body. + // + // Recommended to be fully qualified and short (no longer than 256 characters). + // + // Presence of event_name on the log record identifies this record + // as an event. + // + // [Optional]. + // + // Status: [Development] + string event_name = 12; }