-
Notifications
You must be signed in to change notification settings - Fork 122
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
Anonymous Telemetry #41
Comments
We need to spec this out. |
Let us track - training a model (label/train/match/trainMatch phases) No user specific information(field names, connection strings or any other) should be sent |
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 9, 2021
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 10, 2021
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 11, 2021
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 11, 2021
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 11, 2021
navinrathore
added a commit
to navinrathore/zingg-1
that referenced
this issue
Dec 13, 2021
sonalgoyal
added a commit
that referenced
this issue
Dec 17, 2021
Added Google Analytics for telemetry #41
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Understanding Zingg usage in an anonymous way - number of attributes, size of data, pipes, number of runs, time taken for each run will be helpful to build the right features. This should be absolutely anonymous, with no actual data leaving user environment. And user should have the ability to switch it off anytime.
The text was updated successfully, but these errors were encountered: