-
Notifications
You must be signed in to change notification settings - Fork 821
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
Add init attributes in constructor and sync tracing to work with new … #4206
Add init attributes in constructor and sync tracing to work with new … #4206
Conversation
hey @ArtAhmetaj |
Pinging @dyladan, @mayurkale22 and @pichlermarc in an attempt to make this PR gain some traction. The current implementation makes it impossible to make transformations in |
Your tests seem to verify only the |
@ArtAhmetaj checking if you are picking this up. I can pick this up if you don't have the time. |
Add spacing on init attributes line Co-authored-by: Gerhard Stöbich <[email protected]>
Replace truthy value check with loose null check Co-authored-by: Gerhard Stöbich <[email protected]>
Which problem is this PR solving?
This PR fixes issue #4188 in which the span processor on start method lacks attributes since they are set after with an accessor method (setAttributes) and not on the constructor itself.
Short description of the changes
The PR adds constructor attributes to the span which are optional and if they are added from this layer the spanProcessor.onStart method will have context of attributes whenever it is called, this doest not break compatibility since setAttributes is still a valid public method and also the changes needed on wrappers like the Tracer are done.
Spans have added tests on all constructor tests I could find, the current tests should validate tracer functionality correctly.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:
This bug fix should not be noticable since the wrapper tracer call for starting a span should not change functionality (it is only the internal span constructor changing), would like input if I have to change the documentation for the Span constructor itself considering it is @deprecated.