-
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
Add Google Big Query Exporter to Telemetry #34809
Comments
@theluckiestsoul would you implement the exporter? |
@atoulme Thanks for considering my issue! I'd be glad to take on the implementation. I'll get started and make sure to follow any guidelines. Let me know if there’s anything specific you’d like included. |
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 |
Component(s)
No response
Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to manually export and transfer telemetry data to Google Big Query for analysis, which leads to delays and inefficiencies in our data analysis pipeline. Currently, our telemetry system lacks a direct exporter to Google Big Query, forcing us to rely on cumbersome workarounds, such as exporting data to CSV files and then uploading them to Big Query. This manual process is time-consuming, error-prone, and hinders our ability to quickly gain insights from our telemetry data.
By adding a Google Big Query exporter to the telemetry system, we can streamline our data analysis workflow, reduce manual labor, and unlock more timely and accurate insights.
Describe the solution you'd like
I would like to see a Google Big Query exporter integrated into our telemetry system, allowing us to:
This solution would enable us to:
By implementing this solution, we can enhance our telemetry system's capabilities and improve our overall data analysis workflow.
Describe alternatives you've considered
Here are some alternatives I've considered:
Additional context
No response
The text was updated successfully, but these errors were encountered: