Skip to content

feat!: update the observability appendix to include the latest otel semcon #306

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

beeme1mr
Copy link
Member

@beeme1mr beeme1mr commented Apr 14, 2025

This PR

  • update the observability appendix to include the latest otel semcon

Notes

Marking as a draft until we find out if value can be moved out from the body.

https://docs.google.com/document/d/1x9hprUaUNlVCZMtFAqBcj6h50ukpT0hCAli7BzgWsTQ/edit?tab=t.0

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@beeme1mr
Copy link
Member Author

Depends on changes in the Weaver tool in OTel.

open-telemetry/weaver#703

Once Weaver has been updated to support an any type, we can move value out of the body.

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
@beeme1mr beeme1mr marked this pull request as ready for review April 23, 2025 18:04
@beeme1mr beeme1mr requested a review from toddbaert as a code owner April 23, 2025 18:04
@beeme1mr beeme1mr marked this pull request as draft April 23, 2025 18:05
@beeme1mr
Copy link
Member Author

I've updated the spec to include all the changes recommended by the OTel team. It's ready to be reviewed but we shouldn't merge it until the OTel tooling has been merged.

FYI @kinyoklion

Copy link
Contributor

@dyladan dyladan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally looks good to me. I think it would be better if there was more guidance about when to use variant vs value.

Comment on lines +69 to +70
[^1]: The `variant` field is required if the `value` field is not set.
[^2]: The `value` field is required if the `variant` field is not set.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is technically correct, but I think it doesn't communicate clearly when you would use one or the other. In openfeature you almost always want variant right? value is only there as a fallback for when variant doesn't exist or isn't meaningful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants