Skip to content
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

Open
theluckiestsoul opened this issue Aug 22, 2024 · 3 comments
Open

Add Google Big Query Exporter to Telemetry #34809

theluckiestsoul opened this issue Aug 22, 2024 · 3 comments
Labels
Sponsor Needed New component seeking sponsor Stale

Comments

@theluckiestsoul
Copy link

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:

  1. Automatically export telemetry data to Google Big Query in real-time or at scheduled intervals.
  2. Configure the exporter to select specific telemetry data streams, filter data, and define data formats (e.g., JSON or Avro).
  3. Authenticate using a service account or API key to secure data transfer.
  4. Monitor export status, errors, and data transfer metrics through the telemetry system's UI or API.
  5. Support for partitioning data in Big Query based on date, device ID, or other relevant fields.

This solution would enable us to:

  • Streamline our data analysis pipeline
  • Reduce manual labor and errors
  • Increase data freshness and accuracy
  • Unlock more timely and insightful analytics
  • Leverage Google Big Query's scalability and analytics capabilities

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:

  1. Custom Scripting
  2. Cloud Function
  3. Manual Export and Upload

Additional context

No response

@theluckiestsoul theluckiestsoul added enhancement New feature or request needs triage New item requiring triage labels Aug 22, 2024
@crobert-1 crobert-1 added Sponsor Needed New component seeking sponsor and removed enhancement New feature or request labels Aug 22, 2024
@atoulme
Copy link
Contributor

atoulme commented Oct 2, 2024

@theluckiestsoul would you implement the exporter?

@atoulme atoulme removed the needs triage New item requiring triage label Oct 2, 2024
@theluckiestsoul
Copy link
Author

@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.

Copy link
Contributor

github-actions bot commented Dec 9, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sponsor Needed New component seeking sponsor Stale
Projects
None yet
Development

No branches or pull requests

3 participants