-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/azuredataexplorer] Accept exporterhelper config for azure data explorer exporter #24329
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @david-esteves-sh cc: @asaharn @kustonaut |
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. |
…#27272) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Added support for Exporter Helper configuration. **Link to tracking Issue:** #24329 **Testing:** <Describe what testing was performed and which tests were added.> Added tests and manually tested with e2e scenarios --------- Co-authored-by: Ramachandran A G <[email protected]> Co-authored-by: Ziqi Zhao <[email protected]> Co-authored-by: Ramachandran A G <[email protected]>
Hi @crobert-1 , @david-esteves-sh , This PR is now merged. Can this issue be closed! |
Absolutely, thanks for letting me know! Fixed by #27272 |
…open-telemetry#27272) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Added support for Exporter Helper configuration. **Link to tracking Issue:** open-telemetry#24329 **Testing:** <Describe what testing was performed and which tests were added.> Added tests and manually tested with e2e scenarios --------- Co-authored-by: Ramachandran A G <[email protected]> Co-authored-by: Ziqi Zhao <[email protected]> Co-authored-by: Ramachandran A G <[email protected]>
…open-telemetry#27272) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Added support for Exporter Helper configuration. **Link to tracking Issue:** open-telemetry#24329 **Testing:** <Describe what testing was performed and which tests were added.> Added tests and manually tested with e2e scenarios --------- Co-authored-by: Ramachandran A G <[email protected]> Co-authored-by: Ziqi Zhao <[email protected]> Co-authored-by: Ramachandran A G <[email protected]>
Component(s)
exporter/azuredataexplorer
Is your feature request related to a problem? Please describe.
I am currently using the AzureDataExplorer exporter from the opentelemetry-collector-contrib and do not know of a way to configure the throughput or persistence with the current configuration. The current implementation already uses the ExportHelper but the
queue_settings
values are not configurable. I would like to be able to tweak the configuration to maximize throughput and also use the storage queue options to prevent data loss on shutdown.Describe the solution you'd like
Allow to pass in
sending_queue
,retry_on_failure
andtimeout
config values from the export helper as supported in many other exporters (e.g. otlpexporter, kafkaexporter, etc). Either for the entire exporter or per telemetry type, we could have it configurable by for metrics, logs, traces all separately as a lot of the config today seems to beor
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: