Skip to content

Allow event body to represent a display message #3343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
trask merged 9 commits into from
Feb 17, 2026
Merged

Allow event body to represent a display message #3343

Show file tree
Hide file tree
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
b3d8e78
Update event body usage guidelines to allow representation of display…
pellared Jan 27, 2026
0a00a99
add changelog entry
pellared Jan 27, 2026
b96f18c
Update 3343.yaml
pellared Jan 27, 2026
c54e199
Update 3343.yaml
pellared Jan 27, 2026
60bda62
Update docs/general/events.md
pellared Jan 30, 2026
d4c6008
Revert semconv specific rules
pellared Feb 12, 2026
151d4a6
Merge branch 'main' into evt-body
pellared Feb 17, 2026
c07676a
refine event body usage guidelines in semantic conventions
pellared Feb 17, 2026
6ebeb5e
Update docs/general/events.md
trask Feb 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .chloggen/3343.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
change_type: enhancement
component: event
note: Allow event body to represent a display message.
issues: [3343]
5 changes: 3 additions & 2 deletions docs/general/events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,11 @@ Semantic conventions that define events MUST document the event name and its att
* [Attributes](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.54.0/specification/logs/data-model.md#field-attributes)
SHOULD be used to represent details and provide additional context about the event.

* Events SHOULD NOT use [body](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.54.0/specification/logs/data-model.md#field-body).

* Events SHOULD specify a [severity number](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.54.0/specification/logs/data-model.md#field-severitynumber).

* Events SHOULD NOT use [body](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.54.0/specification/logs/data-model.md#field-body)
except of a string display message of the event.
Comment thread
trask marked this conversation as resolved.
Outdated

## External event compatibility

When recording events from an existing system as OpenTelemetry Events, it's common
Expand Down
Loading