-
Notifications
You must be signed in to change notification settings - Fork 889
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
Remove underspecified and unused Span decorator from Trace SDK. #3363
Conversation
cdcb205
to
a14c04b
Compare
a14c04b
to
6ba4a82
Compare
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.
@tsloughter I remember this was discussed already but I can't find the related issue. Can you please link it to your PR?
I don't think there is an issue (and didn't find one after a quick search). It was discussed in a Spec SIG meeting. |
specification/trace/semantic_conventions/instrumentation/aws-lambda.md
Outdated
Show resolved
Hide resolved
a081f97
to
77c8edd
Compare
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.
LGTM provided @Aneurysm9 comment is addressed. This also looks like a stray change to me.
Changes
This removes the "decorate" language from span processors. Technically a breaking change but since consensus seemed to be that something new needed to be designed I figured it best to get it out of the spec first.
Open question if the "for advanced scenarios such as tagging or filtering" part should be left in. I'd say it doesn't apply to custom processors but you technically could use them to do that in OnStart.