-
Notifications
You must be signed in to change notification settings - Fork 40
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.
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
feat: add appendix D (observability) #287
Conversation
toddbaert
commented
Dec 16, 2024
- adds small appendix section to spec that defines how particular SDK fields are mapped to the recently merge OTel semantics
- this allows providers and hooks to export OTel data consistently for easy interop
- adds a couple supporting glossary liks
8dd27f0
to
fcbbf2a
Compare
Signed-off-by: Todd Baert <[email protected]>
fcbbf2a
to
2d44c6d
Compare
I've marked as draft for now since theres some ongoing conversations in OTel about how to represent certain types of event data: open-telemetry/semantic-conventions#1651 (comment) |
Signed-off-by: Todd Baert <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, we might consider the PR I mentioned regarding the value_type
, but I think we could also start with the value as any
type and add the type hint from the PR later as it does not change the any type.
Signed-off-by: Todd Baert <[email protected]>
e3ff639
to
d71366d
Compare
Signed-off-by: Todd Baert <[email protected]>
Merged with just 3 approvals since we have a diverse set and this is just an appendix. |