-
Notifications
You must be signed in to change notification settings - Fork 113
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
Update kedro-viz telemetry to reflect recent changes in kedro-telemetry #2020
Comments
Thanks for opening this @DimedS. Help me understand: what would be the user-facing consequences of releasing Kedro without making these changes in Kedro-Viz? |
Based on the Viz code, if users disable telemetry using new environment variables but still have a
|
Thanks. Linking the code for reference kedro-viz/package/kedro_viz/integrations/kedro/telemetry.py Lines 18 to 31 in e719f30
|
Perhaps |
I agree; it makes sense to depend on |
Discussed with @jitu5, it makes sense to import the following functions from
However, the user can manually remove |
Make sense to reuse what we already have, @astrojuanlu @rashidakanchwala wdyt ? |
👍🏼 About reusing the code or not, I leave it in your hands! |
Description
We switched to an opt-out model in Kedro-Telemetry as described in issue #715. This change introduces new methods for obtaining telemetry consent, which should be incorporated into the Viz telemetry. Additionally, a new way to establish the user ID was introduced in PR #596, and this should also be updated in Viz.
Context
Why is this change important to you? How would you use it? How can it benefit other users?
Possible Implementation
(Optional) Suggest an idea for implementing the addition or change.
Possible Alternatives
(Optional) Describe any alternative solutions or features you've considered.
Checklist
The text was updated successfully, but these errors were encountered: