-
Notifications
You must be signed in to change notification settings - Fork 55
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
Support sampling_relevant attributes #68
Support sampling_relevant attributes #68
Conversation
Please add a test to https://github.com/open-telemetry/build-tools/blob/main/semantic-conventions/src/tests/semconv/templating/test_markdown.py (plus accompanying input.md, expected.md and minimal yaml file with any name). Then this LGTM 👍 |
I don't know when I'll get a chance to work on this. Simple spec update turned out to be way too complicated. |
Done! |
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.
changelog and version.py should probably be updated.
@mariojonke I can handle that in #67 or a follow-up. |
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.
Thank you!
4967e2d
to
91d7295
Compare
I updated the changelog and version. If it still looks good, can someone please merge it? Thanks! |
@open-telemetry/specs-approvers This will affect the semantic conventions we have in the spec, please take a look. |
Current semantic conventions don't use Here's the change where I start using |
@Oberon00 @arminru @mariojonke can someone please merge it? |
Only the TC can merge PRS in this repo, same as the spec (so @arminru can merge). IMHO we can merge this, because as you said the current spec does not use sampling_relevant. |
Fair enough as the actual usage of it will still be reviewed in the spec. |
thank you all! |
Related to open-telemetry/opentelemetry-specification#1916