Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Commit

Permalink
feedback
Browse files Browse the repository at this point in the history
  • Loading branch information
@trask
trask committed Aug 28, 2024
1 parent f4a9f43 commit 5c2ab4b
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion text/9999-event-vision.md → text/0265-event-vision.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,11 @@ This helps reinforce the idea that events are just a specific type of log.

Note: Because of this, generic event processors should be implemented as Log SDK processors.

OpenTelemetry will recommend that
[instrumentation libraries](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#instrumentation-library)
use the Event API over emitting event via a traditional logging library in order to give users a simple and consistent
onboarding story that doesn't involve mixing the two approaches.

### SDK

The Event SDK needs to support two destinations for events:
Expand All @@ -57,4 +62,4 @@ TODO

## Future possibilities

TODO
The Event API will probably need an `IsEnabled` function based on severity level, scope name, and event name.

0 comments on commit 5c2ab4b

Please sign in to comment.