-
Notifications
You must be signed in to change notification settings - Fork 295
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
v3/integrations/nrawssdk-v2: Grab the NR Transaction from the Context when txn is not set #328
Conversation
Merging develop to create v3.13.0
@RichVanderwal Just wanted to bump this PR. We're currently pulling in our fork for our application, so I'm hoping we can get this (or something equivalent) merged sooner than later. Thanks! |
Thanks, @nc-wittj , I understand maintaining your own fork takes extra time and attention. We're working this into the plan for this month's release. |
@RichVanderwal cool, thanks! Just wanted to make sure it didn't slip through the cracks. 😄 |
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 is great. Thanks for the careful re-working of the tests, too! 👍
example change to support PR #328, plus CHANGELOG.md
Links
#288 (comment)
Details
Allows not needing to individually wrap each AWS API call, by just leveraging the context that is present in the middleware. This allows setting up the New Relic integration once with the AWS config, and any AWS client that uses that AWS config will be automatically integrated with New Relic.
Shoutout to @HenriBeck for noticing this!