-
Notifications
You must be signed in to change notification settings - Fork 652
Add AWS X-Ray Propagator #462
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
Conversation
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 like it copies parts of the ECS resource detector. Could you depend on it instead?
@jmacd Hi Josh, I accidentally merged into our fork. I removed the ECS resource detector parts - could you take a look again? Thanks |
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.
Looks good overall.
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.
The blocking issue here is the package name and the import path not matching.
* add AWS X-Ray propagator and tests * made naming convention changes to adhere to linter * added comment to interface implementation for clarity * update naming convention and added description for method
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.
👍
The methods on the `Float64Gauge`, `Int64Gauge`, `Float64Counter`, `Int64Counter`, `Float64Measure`, and `Int64Measure` `struct`s do not need to mutate the internal state of the `struct` and can therefore be defined with value receivers instead. This aligns closer to the function signatures of each instruments constructor function. Additionally, this change means calls to these methods do not need an allocation to the heap. Resolves #440 Co-authored-by: Rahul Patel <[email protected]>
Which problem is this PR solving?
This PR adds a propagator for propgating AWS X-Ray headers so that AWS X-Ray is able to receive and read traces from the OpenTelemetry Go SDK.
Short description of the changes
cc: @alolita