-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add Queuing, retry and timeout settings to AWS S3 exporter #36264
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Sounds good. |
@stephenhong I can work on this, unless you're planning to implement it. Let me know! |
Yes, please do. Thank you |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Queueing implemented here: |
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Implements the common queueing feature into the `awss3exporter`, as suggested [here](#36264).
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Implements the common queueing feature into the `awss3exporter`, as suggested [here](open-telemetry#36264).
Component(s)
exporter/awss3
Is your feature request related to a problem? Please describe.
There is no configuration option for queuing, retry and timeout for the AWS S3 exporter. I see that the exporterhelper is part of the factory.go but when I tried to use the options in my config.yaml, the collector wouldn't start
Describe the solution you'd like
I believe adding it in the config.go like this would add the options available
Describe alternatives you've considered
No response
Additional context
If the queuing, retry and timeout settings were left out intentionally, may I ask why they had to be taken out?
The text was updated successfully, but these errors were encountered: