-
Notifications
You must be signed in to change notification settings - Fork 759
Configurable max backoff for GRPC exporter #4333
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
Configurable max backoff for GRPC exporter #4333
Conversation
|
Bump. I don't think there is any potential downside to merging this |
|
bump: this is super small, ez to review, and fixes a real problem |
tammy-baylis-swi
left a comment
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.
Lgtm, thanks for the HTTP equivalent links. Please could you resolve the merge conflict?
9963542 to
f43c845
Compare
|
Sorry I missed the notification, should be good to merge now ! |
|
So, any plans to get it finally merged ? |
|
Hi @open-telemetry/python-maintainers please take a look. (I can't do merges) |

Description
Fixes #4331
This makes it so
_create_exp_backoff_generatoris called withself._MAX_RETRY_TIMEOUTinstead of a local var in the grpc exporter. like absolutely everywhere else (HTTP log exporter, HTTP span exporter, ...).Type of change
Please delete options that are not relevant.
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 Contrib Repo Change?
Checklist: