From 846d54be2b16104138cdd34fa29e41a9561bbd0d Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:45:17 +0200 Subject: [PATCH 01/13] Bring back `event.name` attribute Fixes #2597 --- docs/registry/attributes/event.md | 4 +++- model/event/deprecated/registry-deprecated.yaml | 12 +----------- model/event/registry.yaml | 17 +++++++++++++++++ 3 files changed, 21 insertions(+), 12 deletions(-) create mode 100644 model/event/registry.yaml diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index 41eac0c4ee..d093ea3149 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -9,4 +9,6 @@ Attributes for Events represented using Log Records. | Attribute | Type | Description | Examples | Stability | |---|---|---|---|---| -| `event.name` | string | Identifies the class / type of event. | `browser.mouse.click`; `device.app.lifecycle` | ![Deprecated](https://img.shields.io/badge/-deprecated-red)
Replaced by EventName top-level field on the LogRecord. | +| `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | + +**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. diff --git a/model/event/deprecated/registry-deprecated.yaml b/model/event/deprecated/registry-deprecated.yaml index 701f3ba0a6..c726b71fc5 100644 --- a/model/event/deprecated/registry-deprecated.yaml +++ b/model/event/deprecated/registry-deprecated.yaml @@ -4,14 +4,4 @@ groups: display_name: Event Attributes brief: > Attributes for Events represented using Log Records. - attributes: - - id: event.name - type: string - stability: development - deprecated: - reason: uncategorized - note: > - Replaced by EventName top-level field on the LogRecord. - brief: > - Identifies the class / type of event. - examples: ["browser.mouse.click", "device.app.lifecycle"] + attributes: [] diff --git a/model/event/registry.yaml b/model/event/registry.yaml new file mode 100644 index 0000000000..2d29e17c4e --- /dev/null +++ b/model/event/registry.yaml @@ -0,0 +1,17 @@ +groups: + - id: registry.event + type: attribute_group + display_name: Event Attributes + brief: > + Attributes for Events represented using Log Records. + attributes: + - id: event.name + type: string + stability: development + brief: > + Identifies the class / type of event. + note: > + This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName + and by applications using existing logging libraries to add event name information that can be + processed by SDK or Collector components to set the EventName on log records. + examples: ["browser.mouse.click", "device.app.lifecycle"] From 12d2cf39eef48cf842c230da616d5d6720d75aea Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:47:42 +0200 Subject: [PATCH 02/13] add changelog entry --- .chloggen/2597.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 .chloggen/2597.yaml diff --git a/.chloggen/2597.yaml b/.chloggen/2597.yaml new file mode 100644 index 0000000000..f5b178d172 --- /dev/null +++ b/.chloggen/2597.yaml @@ -0,0 +1,8 @@ +change_type: enhancement +component: event +note: "Revive `event.name` attribute for use by non-OTLP exporters and logging libraries." +issues: [2597] +subtext: | + The `event.name` attribute is now undeprecated and can be used by: + - Non-OTLP exporters (e.g., console/stdout exporters) to emit the EventName + - Applications using existing logging libraries to add event name information that can be processed by SDK or Collector components From 752fc3d94aa309e9f0adf3d824635d3ccca3886e Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:49:44 +0200 Subject: [PATCH 03/13] rm registry-deprecated.yaml --- model/event/deprecated/registry-deprecated.yaml | 7 ------- 1 file changed, 7 deletions(-) delete mode 100644 model/event/deprecated/registry-deprecated.yaml diff --git a/model/event/deprecated/registry-deprecated.yaml b/model/event/deprecated/registry-deprecated.yaml deleted file mode 100644 index c726b71fc5..0000000000 --- a/model/event/deprecated/registry-deprecated.yaml +++ /dev/null @@ -1,7 +0,0 @@ -groups: - - id: registry.event.deprecated - type: attribute_group - display_name: Event Attributes - brief: > - Attributes for Events represented using Log Records. - attributes: [] From 328c219bec365ac5fc2517444632646082a4f6ea Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:52:09 +0200 Subject: [PATCH 04/13] update issue templates --- .github/ISSUE_TEMPLATE/bug_report.yaml | 1 + .github/ISSUE_TEMPLATE/change_proposal.yaml | 1 + .github/ISSUE_TEMPLATE/new-conventions.yaml | 1 + 3 files changed, 3 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml index 2112d90db5..2fa1a39f03 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yaml +++ b/.github/ISSUE_TEMPLATE/bug_report.yaml @@ -49,6 +49,7 @@ body: - area:elasticsearch - area:enduser - area:error + - area:event - area:exception - area:faas - area:feature-flag diff --git a/.github/ISSUE_TEMPLATE/change_proposal.yaml b/.github/ISSUE_TEMPLATE/change_proposal.yaml index c0999b4bc0..3cc14bf098 100644 --- a/.github/ISSUE_TEMPLATE/change_proposal.yaml +++ b/.github/ISSUE_TEMPLATE/change_proposal.yaml @@ -41,6 +41,7 @@ body: - area:elasticsearch - area:enduser - area:error + - area:event - area:exception - area:faas - area:feature-flag diff --git a/.github/ISSUE_TEMPLATE/new-conventions.yaml b/.github/ISSUE_TEMPLATE/new-conventions.yaml index 2e8c7b7293..ff72d86a9a 100644 --- a/.github/ISSUE_TEMPLATE/new-conventions.yaml +++ b/.github/ISSUE_TEMPLATE/new-conventions.yaml @@ -52,6 +52,7 @@ body: - area:elasticsearch - area:enduser - area:error + - area:event - area:exception - area:faas - area:feature-flag From 882498bde9517f927f2da2858197751628d86d3d Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:53:21 +0200 Subject: [PATCH 05/13] remove spaces --- docs/registry/attributes/event.md | 2 +- model/event/registry.yaml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index d093ea3149..c5ed2dd0f2 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -11,4 +11,4 @@ Attributes for Events represented using Log Records. |---|---|---|---|---| | `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | -**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. +**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. diff --git a/model/event/registry.yaml b/model/event/registry.yaml index 2d29e17c4e..c74c9a2281 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -11,7 +11,7 @@ groups: brief: > Identifies the class / type of event. note: > - This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName - and by applications using existing logging libraries to add event name information that can be + This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName + and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. examples: ["browser.mouse.click", "device.app.lifecycle"] From 0289423185b347343f69d5a0ebc1d651bdc41212 Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:54:31 +0200 Subject: [PATCH 06/13] fmt --- docs/registry/attributes/event.md | 2 +- model/event/registry.yaml | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index c5ed2dd0f2..16620b5fc2 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -11,4 +11,4 @@ Attributes for Events represented using Log Records. |---|---|---|---|---| | `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | -**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. +**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. diff --git a/model/event/registry.yaml b/model/event/registry.yaml index c74c9a2281..33fe158010 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -11,7 +11,8 @@ groups: brief: > Identifies the class / type of event. note: > - This attribute is used by non-OTLP exporters (e.g., console/stdout exporter) to emit the EventName - and by applications using existing logging libraries to add event name information that can be - processed by SDK or Collector components to set the EventName on log records. + This attribute is used by non-OTLP exporters (e.g., console exporter) + to emit the EventName and by applications using existing logging + libraries to add event name information that can be processed by SDK + or Collector components to set the EventName on log records. examples: ["browser.mouse.click", "device.app.lifecycle"] From 966343a76c528bf249971ea87aa05148827497c9 Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Wed, 3 Sep 2025 10:59:39 +0200 Subject: [PATCH 07/13] cleanup --- .chloggen/2597.yaml | 2 +- docs/registry/attributes/event.md | 2 +- model/event/registry.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.chloggen/2597.yaml b/.chloggen/2597.yaml index f5b178d172..ec0cd17e56 100644 --- a/.chloggen/2597.yaml +++ b/.chloggen/2597.yaml @@ -4,5 +4,5 @@ note: "Revive `event.name` attribute for use by non-OTLP exporters and logging l issues: [2597] subtext: | The `event.name` attribute is now undeprecated and can be used by: - - Non-OTLP exporters (e.g., console/stdout exporters) to emit the EventName + - Non-OTLP exporters (e.g. console exporter) to emit the EventName - Applications using existing logging libraries to add event name information that can be processed by SDK or Collector components diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index 16620b5fc2..8dab51a1b9 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -11,4 +11,4 @@ Attributes for Events represented using Log Records. |---|---|---|---|---| | `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | -**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g., console exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. +**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g. console exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. diff --git a/model/event/registry.yaml b/model/event/registry.yaml index 33fe158010..6575eeced6 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -11,7 +11,7 @@ groups: brief: > Identifies the class / type of event. note: > - This attribute is used by non-OTLP exporters (e.g., console exporter) + This attribute is used by non-OTLP exporters (e.g. console exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. From abf4fcd8d4e820580ca47f69e7af96c7985280ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Thu, 4 Sep 2025 10:59:07 +0200 Subject: [PATCH 08/13] Update .chloggen/2597.yaml Co-authored-by: Liudmila Molkova --- .chloggen/2597.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.chloggen/2597.yaml b/.chloggen/2597.yaml index ec0cd17e56..ba236455c2 100644 --- a/.chloggen/2597.yaml +++ b/.chloggen/2597.yaml @@ -4,5 +4,5 @@ note: "Revive `event.name` attribute for use by non-OTLP exporters and logging l issues: [2597] subtext: | The `event.name` attribute is now undeprecated and can be used by: - - Non-OTLP exporters (e.g. console exporter) to emit the EventName + - Non-OTLP exporters to emit the EventName - Applications using existing logging libraries to add event name information that can be processed by SDK or Collector components From e5bfcf682b6443c580776dc45a168d826e1b0938 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Thu, 4 Sep 2025 10:59:14 +0200 Subject: [PATCH 09/13] Update .chloggen/2597.yaml --- .chloggen/2597.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.chloggen/2597.yaml b/.chloggen/2597.yaml index ba236455c2..1979c02a36 100644 --- a/.chloggen/2597.yaml +++ b/.chloggen/2597.yaml @@ -5,4 +5,4 @@ issues: [2597] subtext: | The `event.name` attribute is now undeprecated and can be used by: - Non-OTLP exporters to emit the EventName - - Applications using existing logging libraries to add event name information that can be processed by SDK or Collector components + - Applications using existing logging libraries to add event name information that can be used to set the EventName field by SDK or Collector components From 1b7bc95a6d4b3bbfea16c0bf6caaacb1d780ac7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Thu, 4 Sep 2025 11:16:18 +0200 Subject: [PATCH 10/13] Update model/event/registry.yaml --- model/event/registry.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/model/event/registry.yaml b/model/event/registry.yaml index 6575eeced6..e3481a1050 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -11,8 +11,9 @@ groups: brief: > Identifies the class / type of event. note: > - This attribute is used by non-OTLP exporters (e.g. console exporter) - to emit the EventName and by applications using existing logging - libraries to add event name information that can be processed by SDK - or Collector components to set the EventName on log records. + This attribute SHOULD be used by non-OTLP exporters + when destination does not support `EventName` or equivalent property. + This attribute MAY be used by applications using existing logging + libraries that does not support `EventName` or equivalent property + so that it can be used to set the `EventName` field by Collector or SDK components. examples: ["browser.mouse.click", "device.app.lifecycle"] From e8e15fae788ee9c9b35d9c8d5d1ff2349afb4235 Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Thu, 4 Sep 2025 11:20:14 +0200 Subject: [PATCH 11/13] refine --- .chloggen/2597.yaml | 4 ++-- model/event/registry.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.chloggen/2597.yaml b/.chloggen/2597.yaml index 1979c02a36..3f01b2fd9a 100644 --- a/.chloggen/2597.yaml +++ b/.chloggen/2597.yaml @@ -4,5 +4,5 @@ note: "Revive `event.name` attribute for use by non-OTLP exporters and logging l issues: [2597] subtext: | The `event.name` attribute is now undeprecated and can be used by: - - Non-OTLP exporters to emit the EventName - - Applications using existing logging libraries to add event name information that can be used to set the EventName field by SDK or Collector components + - Non-OTLP exporters to emit the `EventName` + - Applications using existing logging libraries to add event name information that can be used to set the `EventName` field by Collector or SDK components diff --git a/model/event/registry.yaml b/model/event/registry.yaml index e3481a1050..18a5b7951d 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -14,6 +14,6 @@ groups: This attribute SHOULD be used by non-OTLP exporters when destination does not support `EventName` or equivalent property. This attribute MAY be used by applications using existing logging - libraries that does not support `EventName` or equivalent property - so that it can be used to set the `EventName` field by Collector or SDK components. + libraries so that it can be used to set the `EventName` field by + Collector or SDK components. examples: ["browser.mouse.click", "device.app.lifecycle"] From 531d3da2b74b283804df003db83ed528d2a415bb Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Thu, 4 Sep 2025 11:21:25 +0200 Subject: [PATCH 12/13] regenerate --- docs/registry/attributes/event.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index 8dab51a1b9..1b2160e441 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -11,4 +11,4 @@ Attributes for Events represented using Log Records. |---|---|---|---|---| | `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | -**[1] `event.name`:** This attribute is used by non-OTLP exporters (e.g. console exporter) to emit the EventName and by applications using existing logging libraries to add event name information that can be processed by SDK or Collector components to set the EventName on log records. +**[1] `event.name`:** This attribute SHOULD be used by non-OTLP exporters when destination does not support `EventName` or equivalent property. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the `EventName` field by Collector or SDK components. From 82042ada5cdd51675f06ccf060551556a5c63a6c Mon Sep 17 00:00:00 2001 From: Robert Pajak Date: Thu, 4 Sep 2025 11:26:46 +0200 Subject: [PATCH 13/13] property -> field --- docs/registry/attributes/event.md | 2 +- model/event/registry.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/registry/attributes/event.md b/docs/registry/attributes/event.md index 1b2160e441..216c9e699a 100644 --- a/docs/registry/attributes/event.md +++ b/docs/registry/attributes/event.md @@ -11,4 +11,4 @@ Attributes for Events represented using Log Records. |---|---|---|---|---| | `event.name` | string | Identifies the class / type of event. [1] | `browser.mouse.click`; `device.app.lifecycle` | ![Development](https://img.shields.io/badge/-development-blue) | -**[1] `event.name`:** This attribute SHOULD be used by non-OTLP exporters when destination does not support `EventName` or equivalent property. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the `EventName` field by Collector or SDK components. +**[1] `event.name`:** This attribute SHOULD be used by non-OTLP exporters when destination does not support `EventName` or equivalent field. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the `EventName` field by Collector or SDK components. diff --git a/model/event/registry.yaml b/model/event/registry.yaml index 18a5b7951d..02acfc1b22 100644 --- a/model/event/registry.yaml +++ b/model/event/registry.yaml @@ -12,7 +12,7 @@ groups: Identifies the class / type of event. note: > This attribute SHOULD be used by non-OTLP exporters - when destination does not support `EventName` or equivalent property. + when destination does not support `EventName` or equivalent field. This attribute MAY be used by applications using existing logging libraries so that it can be used to set the `EventName` field by Collector or SDK components.