Skip to content

Track command options in analytics. #4211

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

Closed
6 tasks done
KristianDD opened this issue Dec 6, 2018 · 0 comments
Closed
6 tasks done

Track command options in analytics. #4211

KristianDD opened this issue Dec 6, 2018 · 0 comments
Assignees
Milestone

Comments

@KristianDD
Copy link
Contributor

KristianDD commented Dec 6, 2018

Is your feature request related to a problem? Please describe.

Currently we have no means of analyzing if and how much a command option is used by the users. This affects our ability to prioritize features and to determinate the severity of issues.

Describe the solution you'd like

There should be a way to analyze option usage.

Testing
1 Make sure that usage-reporting is enabled - tns usage-reporting status, tns usage-reporting enable.
2 Execute a command with --analytics-log-file - tns run android --analytics-log-file ./test.txt.
3 Check in the test.txt file that an Options event has been send.

Acceptance Criteria

  • 1 Options event should be send/written in the analytics-log-file
  • 2 Only one Options event should be send per command(this is essential for analyzing the data later)
  • 3 All sensitive data should be replaced with private placeholder in the data that is sent for tracking (any field that contains password in the key, any field that contains a path or an id). List of options and which are marked as sensitive here and here. Also any detected path will be replace with "_localpath" and the value of any option that has a key containing "password" will be replaced with "private".
  • 4 Event should be sent only when usage-reporting is enabled.
  • 5 The options data should be stored in the label field of the event and should be in json format.
  • 6 Cloud options should also be tracked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants