You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
note: "Add `otel.event.name` attribute for use by non-OTLP exporters and logging libraries."
4
+
issues: [2913]
5
+
subtext: |
6
+
The `otel.event.name` attribute can be used by:
7
+
- Non-OTLP exporters to emit the `EventName`
8
+
- Applications using existing logging libraries to add event name information that can be used to set the `EventName` field by Collector or SDK components
@@ -101,6 +102,18 @@ E.g. for Java the fully qualified classname SHOULD be used in this case.
101
102
|`simple_span_processor`| The builtin SDK simple span processor ||
102
103
|`zipkin_http_span_exporter`| Zipkin span exporter over HTTP ||
103
104
105
+
## OTel Event Attributes
106
+
107
+
Attributes used by non-OTLP exporters to represent OpenTelemetry Event's concepts.
108
+
109
+
**Attributes:**
110
+
111
+
| Key | Stability | Value Type | Description | Example Values |
112
+
|---|---|---|---|---|
113
+
| <aid="otel-event-name"href="#otel-event-name">`otel.event.name`</a> || string | Identifies the class / type of event. [3]|`browser.mouse.click`; `device.app.lifecycle`|
114
+
115
+
**[3]`otel.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.
116
+
104
117
## OTel Scope Attributes
105
118
106
119
Attributes used by non-OTLP exporters to represent OpenTelemetry Scope's concepts.
0 commit comments