-
-
Notifications
You must be signed in to change notification settings - Fork 194
Closed
Milestone
Description
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 injson
format. - 6 Cloud options should also be tracked.
Metadata
Metadata
Assignees
Labels
No labels