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 optional telemetry #102

Closed
krlmlr opened this issue Feb 28, 2024 · 0 comments · Fixed by #111
Closed

Add optional telemetry #102

krlmlr opened this issue Feb 28, 2024 · 0 comments · Fixed by #111
Milestone

Comments

@krlmlr
Copy link
Collaborator

krlmlr commented Feb 28, 2024

We want to know which query types are triggering a fallback to dplyr. For this, we want to collect the structure of the tables involved (with anonymized column names) and the actual query sent (only the failing part). We will post this anonymized data to an endpoint, using a variant of the following code:

print(httr::content(httr::POST('https://duckplyr-telemetry.duckdblabs.com/', httr::content_type('text/plain'), body=si, encode='raw')))

The response is a handle that allows us to identify the request.

The telemetry will be completely opt-in, users will have to set an option to enable it. The first time a fallback occurs, users will see a prompt that allows them to share, opt-in permanently, or opt-out permanently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant