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 5c2ab4b commit e9fce22
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion text/0265-event-vision.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,16 @@ Note: Because of this, generic event processors should be implemented as Log SDK

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
use the Event API over emitting events via a traditional logging library in order to give users a simple and consistent
onboarding story that doesn't involve mixing the two approaches.

OpenTelemetry will recommend that application developers also use the Event API over emitting events via a traditional
logging library since it avoid accidentally emitting (non-event) traditional logs.

Also, recommending the Event API over emitting events via a traditional logging library makes for a clearer overall
OpenTelemetry API story - with first class user facing APIs for traces, metrics, and events,
all suitable for using directly in native instrumentation.

### SDK

The Event SDK needs to support two destinations for events:
Expand Down

0 comments on commit e9fce22

Please sign in to comment.