-
Notifications
You must be signed in to change notification settings - Fork 626
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
Adds back retry_attempts to botocore #275
Adds back retry_attempts to botocore #275
Conversation
138ee52
to
b11c016
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.
for now, I'd leave out "aws.retry_attempts", because it's not specific to AWS.
@@ -153,6 +153,11 @@ def _patched_api_call(self, original_func, instance, args, kwargs): | |||
"aws.request_id", req_id, | |||
) | |||
|
|||
if "RetryAttempts" in metadata: | |||
span.set_attribute( | |||
"aws.retry_attempts", metadata["RetryAttempts"], |
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.
Is aws.retry_attempts
the right choice? The original code seems to just have retry_attempts.
That makes sense to me, as retry attempts, albeit behavior in AWS's boto, is not really in aws-specific construct.
retry attempts actually seems quite generic, it probably should be a semantic convention in the spec.
Thanks for taking a look! Moved back to just plain |
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.
Thanks! LGTM.
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.
Thanks for the PR! It looks great, if you could add an entry to the changelog for this, I can approve and merge.
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.
Thanks!
Thanks for the reviews & project in general :D |
Description
The
retry_attempts
field ininstrumentation-botocore
previously reported how many retries it took botocore to complete an API request (e.g. if the client is rate limited).It was lost during this refactor #150 & and I can't find any comments or issues saying it was intentionally dropped (sorry if I missed this!).
So this PR adds it back :D
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
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.
(Lmk if you want me to add this to the changelog)