Area(s)

area:otel

What's missing?

Scenario 1: exporting event records for non-OTLP exporters

Non-OTLP exporters (e.g. a console/stdout exporter) need to emit EventName .

Scenario 2: emitting event records using logging libraries

Application developers that are already using some existing logging libraries (like log4j) may not want to additionally depend on OTel Logs API in places where they want to emit application-specific event records. Most logging libraries do not have a "event name" or "event ID" concept.

Describe the solution you'd like

Undeprecate and change the description of event.name in https://github.com/open-telemetry/semantic-conventions/blob/main/docs/registry/attributes/event.md

Scenario 1:
The non-OTLP exporters (like stdout exporter) can add event.name attribute when exporting event records.

Scenario 2:
Users of non-OTel logging libraries can add event.name attribute/field when emitting logs. Then the SDK or Collector can be configured with a log record processor that sets the EventName on log records that contain the event.name attribute.
Prior art:

• sdk/log: Add EventNameProcessor example opentelemetry-go#7128

Other attribute keys that were considered:

• otel.event.name - Add otel.event.name attribute to the OTel attributes registry. However, given the feedback it seems that there is a preference to use event.name instead. I tried to summarize here: Revive event.name attribute #2597 (comment)
• otel.event_name - this was the original proposal, @trask gave feedback that having event. scopes it under "event" signal/domain

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}