Describe the use cases for events in greater detail #3969
Conversation
|
@tedsuo are there existing Event API language implementations? I don't see events mentioned in the compliance matrix. |
|
@yurishkuro there is a Java prototype and a Web JS prototype. The API is experimental and still hasn't been exercised, it feels a little too early to add it to the compliance matrix. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
|
At this point, all conversations are resolved and this is ready to merge, except fucking javadoc.io is down which is causing the lint checker to fail. 🫠 "A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable" -Leslie Lamport
|
It is not a required CI check. |
|
@martinkuba @MSNev ping |
) Resolves open-telemetry#3254 and open-telemetry#4045 The PR adds clarity to the features provided by Events, as well as guidance on when it is appropriate to use the Event API. ## Changes * Reorganized the Data Model section for clarity * Include MUST for the requirement that Event `Body` and `Attributes` fields conform to a schema. * Include use cases for when Events are appropriate. * Include a warning that advanced logging features are not currently accessible when using Events.
Resolves #3254 and #4045
The PR adds clarity to the features provided by Events, as well as guidance on when it is appropriate to use the Event API.
Changes
BodyandAttributesfields conform to a schema.