-
Notifications
You must be signed in to change notification settings - Fork 230
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Project Tracking: Event API/Sdk/Definition Working Group (#1702)
* Project Tracking: Event API/Sdk/Definition Working Group * Integrate feedback, simplifying the definition * Remove unnecessary bullet points * More Updates * Set meeting time
- Loading branch information
Showing
1 changed file
with
67 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
### Description | ||
|
||
The Client / RUM Sig is looking to finalize, complete and resolve the outstanding issues / PR's that exist around the Event API / SDK and the Semantic Conventions that defines what an "event" is. | ||
|
||
### Project Board | ||
|
||
Project Board: https://github.com/orgs/open-telemetry/projects/65 | ||
|
||
### Deliverables | ||
|
||
Resolve the outstanding Event Issues / PR's which will define | ||
|
||
* Refine / stabilize event data model describing what an event is, the semantic meaning of event fields, and how they are sent over the network. | ||
* Pave the way for defining event semantic conventions, allowing their schemas to be described in YAML and incorporated into build-tools. | ||
* Define select event semantic conventions, establishing patterns for future event semantic conventions to follow. | ||
* Refine / stabilize event API and any associated features in the SDK. | ||
|
||
#### Required staffing | ||
|
||
* Need: more domain experts willing to define the OTel Event standard | ||
* Need: engineers willing to write prototypes in at least one more language other than JavaScript. Language should be fairly different from JavaScript. | ||
* Need: maintainers or approvers from those languages committed to reviewing the prototypes. | ||
|
||
Project lead(s): | ||
|
||
* @MSNev (JavaScript) | ||
|
||
Sponsoring TC Members: | ||
|
||
* @tigrannajaryan | ||
* @jack-berg | ||
|
||
Contributing Engnieers: | ||
|
||
* @martinkuba (JavaScript) | ||
* @scheler | ||
* @patrickhousley | ||
* @breedx-splk | ||
|
||
Implementation Engineers: | ||
* @dennisme (Golang) | ||
|
||
Implementation Maintainers / Approvers: | ||
|
||
* @MSNev | ||
* @martinkuba | ||
* @scheler | ||
|
||
### Meeting Times | ||
|
||
SIG meeting times: Friday 10am - 11am PT | ||
|
||
### Timeline | ||
|
||
By end of 2023 | ||
|
||
* Refine data model (By end of 2023) | ||
* Accommodate events in semantic conventions | ||
* Refine / stabilize API & SDKs | ||
|
||
### Linked Issues and PRs | ||
|
||
See the project board for a collection of Issues related to the project. | ||
|
||
### Labels | ||
|
||
Additional labels to be able to identify "Event" related Issues / PR's would be ideal to help with tracking. |