feat(tracer): support for external observability providers #4902
+832
−31
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pull-request-size
bot
added
the
size/L
7 tasks
boring-cyborg
bot
added
the
dependencies
2 tasks
pull-request-size
bot
added
size/XL
|
leandrodamascena
added
the
on-hold
|
This PR does not introduce any drastic changes and will be merged after the release of V3. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: #2030
Disclaimer
The original PR was created by @roger-zhangg. Due to lot of merge conflicts, we had to close that to merge it into the V3 branch.
Summary
Changes
Some of our customers have asked for the ability to use external observability providers with our Tracer utility in the Powertools for AWS Lambda.
This pull request does not add any new providers, but instead paves the way for them to be integrated in the future. This improvement provides more flexibility and options for our customers, allowing them to tailor their observability setup to their specific needs. The implementation follows our existing Tracer interface, making it easy to use and integrate.
User experience
This change doesn't affect users who just use default AWS X-Ray provider.
This change allows users to bring their own tracer provider to use other solution provider other than AWS X-Ray
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.